- 10 1月, 2019 9 次提交
-
-
由 Melanie Plageman 提交于
MergeAttributes was used in atpxPart_validate_spec to get the schema and constraints to make a new leaf partition as part of ADD or SPLIT PARTITION. It was likely used as a convenience, since it already existed, and seems like the wrong function for the job. Previously atpxPart_validate_spec simply hard-coded in false for the relation persistence since the parameter was simply `isTemp`. Once the options for relation persistence were expanded to included unlogged, this paramter was changed to take a relpersistence. In MergeAttributes, for the part which we actually hit when calling it from here (we pass in the schema as NIL and therefore hit only half of the MergeAttributes code) the `supers` parameter is actually that of the parent partition and includes relpersistence, so, by passing in the relpersistence of the parent as relpersistence here, the checks we do around relpersistence are redundant because we are comparing the parent's relpersistence to its own. However, because, currently, this function is only called when we are making a new relation that, because we don't allow a different persistence to be specified for the child would actually just be using the relpersistence of the parent anyway, by passing it in hard-coded we would actually be incorrectly assuming that we are creating a permanent relation always. Since MergeAttributes was overkill, we wrote a new helper function, SetSchemaAndConstraints, to get the schema and constraints of a relation. This function doesn't do very many special validation checks that may be required by callers when using it in the context of partition tables (so user beware), however, it is probably only useful in the context of partition tables because it assumes constraints will be cooked, which, wouldn't be the case for all relations. We split it into two smaller inline functions for clarity. We also felt this would be a useful helper function in general, so we extern'd it. This commit also sets the relpersistence that is used to make the leaf partition when adding a new partition or splitting an existing a partition. makeRangeVar is a function from upstream which is basically a constructor. It sets relpersistence in the RangeVar to a hard-coded value of RELPERSISTENCE_PERMANENT. However, because we use the root partition to get the constraints and column information for the new leaf, after we use the default construction of the RangeVar, we need to set the relpersistence to that of the parent. This commit specifically only sets it back for the case in which we are adding a partition with `ADD PARTITION` or through `SPLIT PARTITION`. Without this commit, a leaf partition of an unlogged table created through `ADD PARTITION` or `SPLIT PARTITION` would incorrectly have its relpersistence set to permanent. Co-authored-by: NAlexandra Wang <lewang@pivotal.io> Co-authored-by: NMelanie Plageman <mplageman@pivotal.io>
-
由 Ashwin Agrawal 提交于
-
由 Ashwin Agrawal 提交于
-
由 Taylor Vesely 提交于
The WalSndCtl can have status information for non-mirror walsender connections, i.e. pg_basebackup connections. Ignore them. Co-authored-by: NAshwin Agrawal <aagrawal@pivotal.io>
-
由 Asim R P 提交于
Now that we allow multipl WanSnd objects, FTS probes need to recognize the WalSnd object corresponding to the mirror. This is achieved by defining Greenplum-specific application name "gp_replication". The mirrors use this application name as a connection parameter. Any other replication connections (backup and log streamer connections initiated by pg_basebackup) do not use this application name. Log streamer replication connection initiated by pg_basebackup should NOT use Grenplum-specific application name. Co-authored-by: NDavid Kimura <dkimura@pivotal.io> Co-authored-by: NAdam Berlin <aberlin@pivotal.io> Co-authored-by: NTaylor Vesely <tvesely@pivotal.io>
-
由 Adam Berlin 提交于
This replication slot is used for WAL replication between primary and mirror segments, and also master and standby. The replication slot is created when a mirror / standby segment is initialized using pg_basebackup. The replication slot is used by primary to keep track of the WAL flush location reported by the mirror. When the mirror disconnects, it allows the primary to retain enough WAL so that the mirror can catchup after reconnecting in future. - defaults max_wal_senders to 10 to allow for basebackup to spin up senders matching upstream - defaults max_replication_slots to 10 instead of 0 - changes gp_basebackup to create a replication slot when a slot name is provided during gpinitsystem - changes gp_basebackup to use streaming replication during gpinitsystem - creates and uses replication slot during full recovery Note: We intend to reason more deeply with the default guc settings in a later feature. Co-authored-by: NDavid Kimura <dkimura@pivotal.io> Co-authored-by: NAsim R P <apraveen@pivotal.io>
-
由 Peter Eisentraut 提交于
This option specifies a replication slot for WAL streaming (-X stream), so that there can be continuous replication slot use between WAL streaming during the base backup and the start of regular streaming replication. Reviewed-by: NMichael Paquier <michael.paquier@gmail.com>
-
由 ZhangJackey 提交于
df19119c eliminate distributed transaction log creation and maintenance on QD (Only a 32K `pg_distributedlog/0000` file exists). Gpexpand will copy data files from QD to new segments, So in the new segments the oldestXID is 3 (loaded from pg_controlfile which copied from QD). After new segments join the cluster, they will maintain the oldestXmin, so it will loop to find the page which is in the distributed transaction log. If the local transaction ID (xid) is huge on new segments, it will lead to a hole between 0000 and TransactionIdToPage(xid), then an error will be raised. In this commit we truncate the distributedlog with cutoff of oldestxid on new segments, then the hole is gone, so the oldestXmin will be initialized to oldestLocalXmin.
-
由 gshaw-pivotal 提交于
- Include how to make Greenplum within docker accessible to SQL editors running on the local machine (outside of docker). - Update the pip install command so that psutil and lockfile are accessible when the make cluster command is executed.
-
- 09 1月, 2019 15 次提交
-
-
由 Georgios Kokolatos 提交于
Reviewed-by: NHeikki Linnakangas <hlinnakangas@pivotal.io> Reviewed-by: NDaniel Gustafsson <dgustafsson@pivotal.io>
-
由 Heikki Linnakangas 提交于
cdbpath_motion_for_join() was sometimes returning an incorrect locus for a join between SingleQE and Hashed loci. This happened, when even the "last resort" strategy to move hashed side to the single QE failed. This can happen at least in the query that's added to the regression tests. The query involves a nested loop join path, when one side is a SingleQE locus and the other side is a Hashed locus, and there are no join predicates that can be used to determine the resulting locus. While we're at it, turn the Assertion that this tripped, and some related ones at the same place, into elog()s. No need to crash the whole server if the planner screws up, and it'd be good to perform these sanity checks in production, too. The failure of the "last resort" codepath was left unhandled by commit 0522e960. Fixes https://github.com/greenplum-db/gpdb/issues/6643. Reviewed-by: NPaul Guo <pguo@pivotal.io>
-
由 Yandong Yao 提交于
-
由 Richard Guo 提交于
The following identity holds true: (A antijoin B on (Pab)) innerjoin C on (Pac) = (A innerjoin C on (Pac)) antijoin B on (Pab) So we should not enforce join ordering for ANTI. Instead we need to collapse ANTI join nodes so that they participate fully in the join order search. For example: select * from a join b on a.i = b.i where not exists (select i from c where a.i = c.i); For this query, the origin join order is "(a innerjoin b) antijoin c". If we enforce ANTI join ordering, this will be the final join order. But another join order "(a antijoin c) innerjoin b" is also legal. We should take this order into consideration and pick a cheaper one. For LASJ, it is the same as ANTI joins. Reviewed-by: NHeikki Linnakangas <hlinnakangas@pivotal.io> Reviewed-by: NMelanie Plageman <mplageman@pivotal.io>
-
由 Ashwin Agrawal 提交于
Co-authored-by: NEkta Khanna <ekhanna@pivotal.io>
-
由 Ashwin Agrawal 提交于
Co-authored-by: NEkta Khanna <ekhanna@pivotal.io>
-
由 Ashwin Agrawal 提交于
With this commit the QE in maintenance mode will ignore the distributed log and just pretend like single instance postgres. Without this if starting QE as single instance only, no distributed snapshot is executed. Due to this distributed oldest xmin points to oldest datfrozen_xid in system. As a result, vacuum any table results in HEAP_TUPLE_RECENTLY_DEAD and avoids cleaning up dead rows. Co-authored-by: NEkta Khanna <ekhanna@pivotal.io>
-
由 Pengzhou Tang 提交于
All lwlocks are stored in MainLWLockArray which is an array of LWLockPadded structures: typedef union LWLockPadded { LWLock lock; char pad[LWLOCK_PADDED_SIZE]; } LWLockPadded; The calculation in SyncHTPartLockId to fetch a lwlock is incorrect because it offsets the array as an LWLock array. In current code base, it works fine because the size of LWLock happens to be 32, if structure LWLock get enlarged, the calculation will mess up.
-
由 Pengzhou Tang 提交于
-
由 Pengzhou Tang 提交于
GPDB always set the REWIND flag for subplans include init plans, in 6195b967, we enhanced the restriction that if a node is not eager free, we cannot squelch a node earlier include init plans, this exposes a few hidden bugs: if init plan contains a motion node that needs to be squelched earlier, the whole query will get stuck in cdbdisp_checkDispatchResult() because some QEs are still keep sending tuples. To resolve this, we use DISPATCH_WAIT_FINISH mode for dispatcher to wait the dispatch results of init plan, init plan with motion is always executed on QD and should always be a SELECT-like plan, init plan must already fetched all the tuples it needed before dispatcher waiting for the QEs, DISPATCH_WAIT_FINISH is the right mode for init plan.
-
由 Ekta Khanna 提交于
Co-authored-by: NJimmy Yih <jyih@pivotal.io>
-
由 Ekta Khanna 提交于
As part of commit dc78e56c, logic for distributed snapshot was modified to use latestCompletedDxid. This changed the logic from xmax being inclusive range to not inclusive for visible transactions in snapshot. Hence, updating the check to return DISTRIBUTEDSNAPSHOT_COMMITTED_INPROGRESS even for transaction id equal to global xmax now. Other way to fix is using latestCompletedDxid without +1 for xmax, but better is to keep logic similar to local snapshot check and not have xmax in inclusive range of visible transactions. This was exposed in CI by test isolation/results/heap-repeatable-read-vacuum-freeze failing intermittently. This was due to isolation framework itself triggering query on pg_locks to check for deadlocks. This commit adds explicitely test to cover the scenario. Co-authored-by: NAshwin Agrawal <aagrawal@pivotal.io>
-
由 Ashwin Agrawal 提交于
With commit 8a11bfff, aggressive restart point creation is not performed in gpdb as well. Since CreateRestartPoint() is not coded to be called from startup process, GPDB specific code exception was added in past to work correctly for previous aggressive restart point creations, calls to which could happen via startup process. Now given only when gp_replica_check is running restartpoint is created on checkpoint record, which should be done via checkpointer process. Eliminate any case of calling CreateRestartPoint() from startup process and thereby remove GPDB added exception to CreateRestartPoint() and align to upstream code.
-
由 Heikki Linnakangas 提交于
The gptransfer behave test was using gpdiff to compare data between the source and target systems, and was relying on gpdiff to mask row order differences. However, after 1f44603a, gpdiff no longer recognized the results as psql result sets, because it did not echo the SELECT statements to the output. gpdiff expects to see those. Fix, by echoing the statements, like in pg_regress. That makes the output, if there are any differences, more readable anyway. While we're at it, change the gpdiff invocation to produce a unified diff. If the test fails, because there is a difference, that makes the output a lot more readable.
-
由 Heikki Linnakangas 提交于
The test was using "-- ignore", to cause gpdiff to ignore any differences in the test output. But after commit 1f44603a, gpdiff doesn't consider the test's output as a psql result set anymore, so the "-- ignore" directive doesn't work anymore. Use the more common "-- start_ignore"/"-- end_ignore" block instead. (I'm not sure how useful the test is, if we don't check the output, but thats a different story.)
-
- 08 1月, 2019 16 次提交
-
-
由 Pengzhou Tang 提交于
Previously, Even a connection has been explicitly set to inactive, the old code might still treat the connection as active if conn->cdbProc is not null and conn->sndQueue is not empty and increase activeCount. In the next loop, because conn->stillActive is true, conn->unackQueue or conn->sndQueue are never be freed and activeCount always be non-zeror and might cause an infinite loop.
-
由 Heikki Linnakangas 提交于
Commit 7d7782f1 changed the formatting of result sets slightly in isolation2 output. I missed changing these expected outputs in that commit.
-
由 Heikki Linnakangas 提交于
Improve the detection of the beginning of a result set. Previously, it would get confused by comments like "-------", which look a lot like the beginning of a single-column psql result set. That doesn't matter much, as long as the test is passing, but if such a test fails, the diff was very difficult to read, as atmsort reordered the SQL lines, too. Make the detection more resilient, by looking at the previous line. In a real psql result set, the previous line should be a header line, like " col1 | col2 ". A header line begins and ends with spaces, anything else means that we're seeing a SQL comment rather than a psql result set. While we're at it, if the "------" line has any leading or trailing whitespace, it's not a psql result set. I'm not sure why we were lenient on that, but let's make that more strict, too. Reviewed-by: NAsim R P <apraveen@pivotal.io>
-
由 Heikki Linnakangas 提交于
Why, you might ask? The next commit will modify the code in gpdiff.pl, so that it doesn't get fooled by "----"-style comments, thinking that they are psql result sets. A side-effect of that is that it would also no longer recognize the result sets in the isolation2 output, without this patch.
-
由 Heikki Linnakangas 提交于
It was removed along with file replication, in commit 5c158ff3.
-
由 Heikki Linnakangas 提交于
These happen easily when merging code from upstream, that had already been backported earlier.
-
由 Heikki Linnakangas 提交于
To make merging and diffing with upstream easier.
-
由 Heikki Linnakangas 提交于
It is created by initdb these days, as hinted by the comment.
-
由 Heikki Linnakangas 提交于
In int8.c: No one compiles GPDB with !USE_FLOAT8_BYVAL. I guess it should work in theory, but it hasn't been tested for ages. This makes int8.c 100% identical to upstream In ruleutils.c: elog(ERROR) never returns, so this was dead code.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
-
由 BaiShaoqi 提交于
Use guc create_restarpoint_on_ckpt_record_replay to create a restartpoint immediately after replaying a checkpoint record (#6595) Reviewed-by: NAshwin Agrawal <aagrawal@pivotal.io> Reviewed-by: NZhenghua Lyu <zlv@pivotal.io> Reviewed-by: NPaul Guo <pguo@pivotal.io>
-
由 Paul Guo 提交于
Fix fts_recovery_in_progress test failure because pg_rewind runs before timeline id updating after mirror promotion. This issue was actually seen on PG upstream and was fixed by Heikki in pg_rewind test case. In gpdb, we are much more automatically using pg_rewind via gprecoverseg, so we'd better fix that in our own code (gprecoverseg or pg_rewind). On gpdb, after mirror promotion via fts, the time is possibly not short before a correct timeline id is flushed into the pg_control file. For such case, if we do incremental recovery via gprecoverseg, it will succeed but the target node (new mirror) is still not functional. commit 484a848a Author: Heikki Linnakangas <heikki.linnakangas@iki.fi> Date: Thu Apr 30 21:57:18 2015 -0700 Fix pg_rewind regression failure after "fast promotion" pg_rewind looks at the control file to determine the server's timeline. If the standby performs a "fast promotion", the timeline ID in the control file is not updated until the next checkpoint. The startup process requests a checkpoint immediately after promotion, so this is unlikely to be an issue in the real world, but the regression suite ran pg_rewind so quickly after promotion that the checkpoint had not yet completed. Reported by Stephen Frost
-
由 Ashwin Agrawal 提交于
Without this commit, after initdb datfrozenxid for all databases remains 3. Ideally, databases should get freezed during initdb as tools like pg_upgrade make assumptions on the same. Co-authored-by: NEkta Khanna <ekhanna@pivotal.io>
-
由 Mel Kiyama 提交于
* docs - first HA updates that use WAL replication. --Removed references to filerep --Updated segment instance states to use WAL rep states --Other misc. updates. * docs - HA updates for WAL replication - review comment upates
-
由 Ashwin Agrawal 提交于
-