[COMMITTERS] pgsql: Unify spelling of canceled, canceling, cancellation
Unify spelling of canceled, canceling, cancellation We had previously (af26857a2775e7ceb0916155e931008c2116632f) established the U.S. spellings as standard. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/21f1e15aafb13ab2430e831a3da7d4d4f525d1ce Modified Files -- doc/src/sgml/high-availability.sgml | 12 doc/src/sgml/indexam.sgml|2 +- doc/src/sgml/libpq.sgml |2 +- doc/src/sgml/monitoring.sgml | 14 +- doc/src/sgml/protocol.sgml |2 +- doc/src/sgml/ref/set_transaction.sgml|2 +- doc/src/sgml/release-7.4.sgml|2 +- doc/src/sgml/release-8.0.sgml|2 +- doc/src/sgml/release-8.1.sgml|4 +- doc/src/sgml/release-8.2.sgml|2 +- doc/src/sgml/release-8.3.sgml|2 +- doc/src/sgml/release-8.4.sgml|2 +- doc/src/sgml/release-9.1.sgml|2 +- src/backend/access/transam/xlog.c| 12 src/backend/commands/vacuum.c|4 +- src/backend/postmaster/autovacuum.c |4 +- src/backend/postmaster/bgwriter.c|2 +- src/backend/storage/buffer/bufmgr.c |2 +- src/backend/storage/lmgr/README-SSI |6 ++-- src/backend/storage/lmgr/deadlock.c |2 +- src/backend/storage/lmgr/predicate.c | 22 src/backend/storage/lmgr/proc.c |2 +- src/backend/tcop/postgres.c |2 +- src/backend/utils/cache/relcache.c |2 +- src/bin/psql/common.c|2 +- src/bin/scripts/common.c |2 +- src/port/path.c |2 +- src/test/regress/expected/prepared_xacts.out |2 +- src/test/regress/expected/subselect.out | 36 +- src/test/regress/sql/subselect.sql | 10 +++--- 30 files changed, 82 insertions(+), 82 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] stackbuilder - wizard: Modified the Stackbuilder to raise a UAC in case
Log Message: --- Modified the Stackbuilder to raise a UAC in case non-administrative user launches the application Modified Files: -- wizard: CMakeLists.txt (r1.27 - r1.28) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/stackbuilder/wizard/CMakeLists.txt?r1=1.27r2=1.28) StackBuilder.cpp (r1.15 - r1.16) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/stackbuilder/wizard/StackBuilder.cpp?r1=1.15r2=1.16) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] stackbuilder - wizard: Improve error messages.
Log Message: --- Improve error messages. Modified Files: -- wizard: StackBuilder.cpp (r1.16 - r1.17) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/stackbuilder/wizard/StackBuilder.cpp?r1=1.16r2=1.17) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Branch refs/heads/REL9_7_STABLE was created
Branch refs/heads/REL9_7_STABLE was created. View: http://git.postgresql.org/pg/shortlog/refs/heads/REL9_7_STABLE -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Branch refs/heads/REL9_7_STABLE was removed
Branch refs/heads/REL9_7_STABLE was removed. -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_7_STABLE was created
Just so people don't panic - this is me testing the policy script :-) //Magnus On Wed, Jun 29, 2011 at 16:31, pg...@postgresql.org wrote: Branch refs/heads/REL9_7_STABLE was created. View: http://git.postgresql.org/pg/shortlog/refs/heads/REL9_7_STABLE -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Branch refs/heads/REL9_7_STABLE was created
Branch refs/heads/REL9_7_STABLE was created. View: http://git.postgresql.org/pg/shortlog/refs/heads/REL9_7_STABLE -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Branch refs/heads/REL9_7_STABLE was removed
Branch refs/heads/REL9_7_STABLE was removed. -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Protect pg_stat_reset_shared() against NULL input
Protect pg_stat_reset_shared() against NULL input Per bug #6082, reported by Steve Haslam Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/3ec6e00ece5fc7483f8890306005f97a2c640861 Modified Files -- src/backend/utils/adt/pgstatfuncs.c | 14 +++--- 1 files changed, 11 insertions(+), 3 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Protect pg_stat_reset_shared() against NULL input
Protect pg_stat_reset_shared() against NULL input Per bug #6082, reported by Steve Haslam Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff/cbfd82aad252fd86b560a7b7c3d87260a34a595e Modified Files -- src/backend/utils/adt/pgstatfuncs.c | 14 +++--- 1 files changed, 11 insertions(+), 3 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Move the PredicateLockRelation() call from nodeSeqscan.c to heap
Move the PredicateLockRelation() call from nodeSeqscan.c to heapam.c. It's more consistent that way, since all the other PredicateLock* calls are made in various heapam.c and index AM functions. The call in nodeSeqscan.c was unnecessarily aggressive anyway, there's no need to try to lock the relation every time a tuple is fetched, it's enough to do it once. This has the user-visible effect that if a seq scan is initialized in the executor, but never executed, we now acquire the predicate lock on the heap relation anyway. We could avoid that by taking the lock on the first heap_getnext() call instead, but it doesn't seem worth the trouble given that it feels more natural to do it in heap_beginscan(). Also, remove the retail PredicateLockTuple() calls from heap_getnext(). In a seqscan, started with heap_begin(), we're holding a whole-relation predicate lock on the heap so there's no need to lock the tuples individually. Kevin Grittner and me Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/f01e3d3a414f909762ab840719aeb8ae291aab5a Modified Files -- src/backend/access/heap/heapam.c | 21 ++--- src/backend/executor/nodeSeqscan.c |6 -- src/include/access/relscan.h |1 - 3 files changed, 14 insertions(+), 14 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Grab predicate locks on matching tuples in a lossy bitmap heap s
Grab predicate locks on matching tuples in a lossy bitmap heap scan. Non-lossy case was already handled correctly. Kevin Grittner Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/1aa447a1e1273e51f1bb34e085c021941db86212 Modified Files -- src/backend/executor/nodeBitmapHeapscan.c | 12 +++- 1 files changed, 11 insertions(+), 1 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Move the PredicateLockRelation() call from nodeSeqscan.c to heap
Move the PredicateLockRelation() call from nodeSeqscan.c to heapam.c. It's more consistent that way, since all the other PredicateLock* calls are made in various heapam.c and index AM functions. The call in nodeSeqscan.c was unnecessarily aggressive anyway, there's no need to try to lock the relation every time a tuple is fetched, it's enough to do it once. This has the user-visible effect that if a seq scan is initialized in the executor, but never executed, we now acquire the predicate lock on the heap relation anyway. We could avoid that by taking the lock on the first heap_getnext() call instead, but it doesn't seem worth the trouble given that it feels more natural to do it in heap_beginscan(). Also, remove the retail PredicateLockTuple() calls from heap_getnext(). In a seqscan, started with heap_begin(), we're holding a whole-relation predicate lock on the heap so there's no need to lock the tuples individually. Kevin Grittner and me Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/cd70dd6bef515a573a5af1756ce6a8b8406bb5d4 Modified Files -- src/backend/access/heap/heapam.c | 21 ++--- src/backend/executor/nodeSeqscan.c |6 -- src/include/access/relscan.h |1 - 3 files changed, 14 insertions(+), 14 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Restore correct btree preprocessing of indexedcol IS NULL cond
Restore correct btree preprocessing of indexedcol IS NULL conditions. Such a condition is unsatisfiable in combination with any other type of btree-indexable condition (since we assume btree operators are always strict). 8.3 and 8.4 had an explicit test for this, which I removed in commit 29c4ad98293e3c5cb3fcdd413a3f4904efff8762, mistakenly thinking that the case would be subsumed by the more general handling of IS (NOT) NULL added in that patch. Put it back, and improve the comments about it, and add a regression test case. Per bug #6079 from Renat Nasyrov, and analysis by Dean Rasheed. Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff/bbfcc71496051651accb71540130c6d36377a692 Modified Files -- src/backend/access/nbtree/nbtutils.c | 17 +- src/test/regress/expected/create_index.out | 48 src/test/regress/sql/create_index.sql |8 + 3 files changed, 71 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Restore correct btree preprocessing of indexedcol IS NULL cond
Restore correct btree preprocessing of indexedcol IS NULL conditions. Such a condition is unsatisfiable in combination with any other type of btree-indexable condition (since we assume btree operators are always strict). 8.3 and 8.4 had an explicit test for this, which I removed in commit 29c4ad98293e3c5cb3fcdd413a3f4904efff8762, mistakenly thinking that the case would be subsumed by the more general handling of IS (NOT) NULL added in that patch. Put it back, and improve the comments about it, and add a regression test case. Per bug #6079 from Renat Nasyrov, and analysis by Dean Rasheed. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/a5652d3e05380edcd35236e94b924c8c105eaefd Modified Files -- src/backend/access/nbtree/nbtutils.c | 17 +- src/test/regress/expected/create_index.out | 48 src/test/regress/sql/create_index.sql |8 + 3 files changed, 71 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Restore correct btree preprocessing of indexedcol IS NULL cond
Restore correct btree preprocessing of indexedcol IS NULL conditions. Such a condition is unsatisfiable in combination with any other type of btree-indexable condition (since we assume btree operators are always strict). 8.3 and 8.4 had an explicit test for this, which I removed in commit 29c4ad98293e3c5cb3fcdd413a3f4904efff8762, mistakenly thinking that the case would be subsumed by the more general handling of IS (NOT) NULL added in that patch. Put it back, and improve the comments about it, and add a regression test case. Per bug #6079 from Renat Nasyrov, and analysis by Dean Rasheed. Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/3b80219e96f2d2b696ed8dc395d468b38d8ef592 Modified Files -- src/backend/access/nbtree/nbtutils.c | 17 +- src/test/regress/expected/create_index.out | 48 src/test/regress/sql/create_index.sql |8 + 3 files changed, 71 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix outdated comment
Fix outdated comment Extracted from a patch by Bernd Helmle Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/b36927fbe922d1aac5d6e42c04eecf65bf37f5f3 Modified Files -- src/backend/parser/parse_utilcmd.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
