[COMMITTERS] pgsql: Resolve timing issue with logging locks for Hot Standby.
Resolve timing issue with logging locks for Hot Standby. We log AccessExclusiveLocks for replay onto standby nodes, but because of timing issues on ProcArray it is possible to log a lock that is still held by a just committed transaction that is very soon to be removed. To avoid any timing issue we avoid applying locks made by transactions with InvalidXid. Simon Riggs, bug report Tom Lane, diagnosis Pavan Deolasee Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/8572cc495cd07d4f4a59624d275a75b45340a3b2 Modified Files -- src/backend/storage/ipc/procarray.c |8 +-- src/backend/storage/ipc/standby.c | 110 --- src/backend/storage/lmgr/lock.c | 12 - src/include/storage/standby.h |2 +- 4 files changed, 88 insertions(+), 44 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Resolve timing issue with logging locks for Hot Standby.
Resolve timing issue with logging locks for Hot Standby. We log AccessExclusiveLocks for replay onto standby nodes, but because of timing issues on ProcArray it is possible to log a lock that is still held by a just committed transaction that is very soon to be removed. To avoid any timing issue we avoid applying locks made by transactions with InvalidXid. Simon Riggs, bug report Tom Lane, diagnosis Pavan Deolasee Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff/a286b6f6c7f6b327fad2a7081d7df88a4c83ce11 Modified Files -- src/backend/storage/ipc/procarray.c |8 +-- src/backend/storage/ipc/standby.c | 110 --- src/backend/storage/lmgr/lock.c | 12 - src/include/storage/standby.h |2 +- 4 files changed, 88 insertions(+), 44 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Properly free the sslcompression field in PGconn
Properly free the sslcompression field in PGconn Marko Kreen Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/21238deea50e194bfa1c844b01ffbd15ed56c01a Modified Files -- src/interfaces/libpq/fe-connect.c |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Implement dry-run mode for pg_archivecleanup
Implement dry-run mode for pg_archivecleanup In dry-run mode, just the name of the file to be removed is printed to stdout; this is so the user can easily plug it into another program through a pipe. If debug mode is also specified, a more verbose message is printed to stderr. Author: Gabriele Bartolini Reviewer: Josh Kupershmidt Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/b2e431a4db81a735d1474c4d1565a20b835878c9 Modified Files -- contrib/pg_archivecleanup/pg_archivecleanup.c | 23 ++- doc/src/sgml/pgarchivecleanup.sgml|9 + 2 files changed, 31 insertions(+), 1 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Try to be more consistent about accepting denormalized float8 nu
Try to be more consistent about accepting denormalized float8 numbers. On some platforms, strtod() reports ERANGE for a denormalized value (ie, one that can be represented as distinct from zero, but is too small to have full precision). On others, it doesn't. It seems better to try to accept these values consistently, so add a test to see if the result value indicates a true out-of-range condition. This should be okay per Single Unix Spec. On machines where the underlying math isn't IEEE standard, the behavior for such small numbers may not be very consistent, but then it wouldn't be anyway. Marti Raudsepp, after a proposal by Jeroen Vermeulen Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/c318aeed84438619fc6b8c647def1730a110f04b Modified Files -- src/backend/utils/adt/float.c | 44 +++- 1 files changed, 34 insertions(+), 10 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Add some regression test cases for denormalized float8 input.
Add some regression test cases for denormalized float8 input. This was submitted with the previous patch, but I'm committing it separately to ease backing it out if these results prove too unportable. Marti Raudsepp, after a proposal by Jeroen Vermeulen Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/500cf66d5522b39ddfdc26b309f8b5b0e385f42e Modified Files -- .../expected/float8-exp-three-digits-win32.out | 19 +++ src/test/regress/expected/float8-small-is-zero.out | 19 +++ .../regress/expected/float8-small-is-zero_1.out| 19 +++ src/test/regress/expected/float8.out | 19 +++ src/test/regress/sql/float8.sql|5 + 5 files changed, 81 insertions(+), 0 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: psql: Case preserving completion of SQL key words
psql: Case preserving completion of SQL key words Instead of always completing SQL key words in upper case, look at the word being completed and match the case. reviewed by Fujii Masao Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/69f4f1c3576abc535871c6cfa95539e32a36120f Modified Files -- src/bin/psql/tab-complete.c | 71 +++--- 1 files changed, 59 insertions(+), 12 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: initdb: Add options --auth-local and --auth-host
initdb: Add options --auth-local and --auth-host reviewed by Robert Haas and Pavel Stehule Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/8a02339e9ba3f2f962c5967be8c5d053a1fa39d2 Modified Files -- doc/src/sgml/ref/initdb.sgml | 31 ++- src/backend/libpq/pg_hba.conf.sample |8 +- src/bin/initdb/initdb.c | 157 ++ 3 files changed, 134 insertions(+), 62 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Avoid re-checking for visibility map extension too frequently.
Avoid re-checking for visibility map extension too frequently. When testing bits (but not when setting or clearing them), we now won't check whether the map has been extended. This significantly improves performance in the case where the visibility map doesn't exist yet, by avoiding an extra system call per tuple. To make sure backends notice eventually, send an smgr inval on VM extension. Dean Rasheed, with minor modifications by me. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/b4e0741727685443657b55932da0c06f028fbc00 Modified Files -- src/backend/access/heap/visibilitymap.c | 25 - 1 files changed, 20 insertions(+), 5 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
