[COMMITTERS] pgsql: Introduce sending servers as new category for replication params

Introduce sending servers as new category for replication params Fujii Masao Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/4bd8ed31b76fde16ee00c123751e25019e4d9854 Modified Files -- src/backend/utils/misc/guc.c | 10 ++ src/ba

[COMMITTERS] pgsql: Minor doc additions for cascading replication.

Minor doc additions for cascading replication. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/6ba77bce9378cb9c5fb89a4d30bf77c2a17b0d64 Modified Files -- doc/src/sgml/config.sgml |2 +- doc/src/sgml/monitoring.sgml |3 ++- 2 files changed, 3 ins

[COMMITTERS] pgsql: Remove superfluous variable.

Remove superfluous variable. Reported by Peter Eisentraut. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/cdd61237d6265fa355afa772ca3eee39e4905bcb Modified Files -- src/backend/commands/indexcmds.c |2 -- 1 files changed, 0 insertions(+), 2 deletions

Re: [COMMITTERS] pgsql: Further thoughts about temp_file_limit patch.

2011/7/17 Tom Lane : > Further thoughts about temp_file_limit patch. > > Move FileClose's decrement of temporary_files_size up, so that it will be > executed even if elog() throws an error.  This is reasonable since if the > unlink() fails, the fact the file is still there is not our fault, and we

Re: [COMMITTERS] pgsql: Further thoughts about temp_file_limit patch.

=?ISO-8859-1?Q?C=E9dric_Villemain?= writes: > How does it sound to remove the stat() call used when log_temp_file is > set in favor of fileSize that we now have ? I'd just as soon keep the stat call --- it's relatively cheap and it guarantees an accurate answer. regards,

[COMMITTERS] pgsql: Some refinement for the "fast path" lock patch.

Some refinement for the "fast path" lock patch. 1. In GetLockStatusData, avoid initializing instance before we've ensured that the array is large enough. Otherwise, if repalloc moves the block around, we're hosed. 2. Add the word "Relation" to the name of some identifiers, to avoid assuming that

[COMMITTERS] pgsql: Remove O(N^2) performance issue with multiple SAVEPOINTs.

Remove O(N^2) performance issue with multiple SAVEPOINTs. Subtransaction locks now released en masse at main commit, rather than repeatedly re-scanning for locks as we ascend the nested transaction tree. Split transaction state TBLOCK_SUBEND into two states, TBLOCK_SUBCOMMIT and TBLOCK_SUBRELEASE t

[COMMITTERS] pgsql: Add expected regress output on stricter isolation levels

Add expected regress output on stricter isolation levels These new files allow the new FK tests on isolationtester to pass on the serializable and repeatable read isolation levels (which are untested by the buildfarm). Author: Kevin Grittner Reviewed by Noah Misch Branch -- master Details -

[COMMITTERS] pgsql: Make isolationtester more robust on locked commands

Make isolationtester more robust on locked commands Noah Misch diagnosed the buildfarm problems in the isolation tests partly as failure to differentiate backends properly; the old code was using backend IDs, which is not good enough because a new backend might use an already used ID. Use PIDs in

[COMMITTERS] pgsql: Increase deadlock_timeout to 100ms in FK isolation tests

Increase deadlock_timeout to 100ms in FK isolation tests The previous value of 20ms is dangerously close to the time actually spent just waiting for the deadlock to happen, so on occasion it causes the test to fail simply because the other session didn't get to run early enough, not managing to ca