gpdb
gpdb copied to clipboard
Greenplum Database - Massively Parallel PostgreSQL for Analytics. An open-source massively parallel data platform for analytics, machine learning and AI.
This patch helps remove redundant base64 encoding and decoding functions in gp_hyperloglog.c and add test cases for gp_hyperloglog. 1. Postgres upstream provides the implementation of base64 encoding and decoding utilities....
About ten years ago, direct dispatch in deep-slice queries has been disabled due to the following case that found DTM issue with targeted dispatch and deepslice queries. ``` set test_print_direct_dispatch_info...
Correctly implement exponential backoff to damp scale factor ## Here are some reminders before you submit the pull request - [ ] Add tests for the change - [ ]...
A segment's dbid uniquely identifies it among all postmasters within a Greenplum cluster. This is primarily used by FTS. This was repurposed for user-defined tablespaces. Each segment would append a...
Append-optimised column oriented (AOCO) tables are organised as one file per column at storage layer. This layout is amenable to optimisation in case of ALTER TABLE ALTER COLUMN command where...
This is backport of https://github.com/greenplum-db/gpdb/pull/13891. Commits start blocking only if STREAMING or CATCHUP within range. In real scenarios it often happens that the mirror node is down (probably not really...
Commits start blocking only if STREAMING or CATCHUP within range. In real scenarios it often happens that the mirror node is down (probably not really down) and out-of-sync for some...
The purpose of this Pull Request is to bring f_smgr interface back to Greenplum storage. SMGR interface present in PostgreSQL source code since its first [git commit ](https://github.com/postgres/postgres/blob/d31084e9d1118b25fd16580d9d8c2924b5740dff/src/backend/storage/smgr/smgr.c#L28). It's very...
Previously in gprecoverseg when we try to stop the segments it was taking too long to get and verify the list of postmaster processes on segments as this part was...
There was a guc repl_catchup_within_range that "Sets the maximum number of xlog segments allowed to lag when the backends can start blocking despite the WAL sender being in catchup phase."...