[COMMITTERS] pgsql: Document that multiple LDAP servers can be specified

Document that multiple LDAP servers can be specified Branch -- REL8_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/3a7368bf336bb97e99c11e11306ee558211eefe6 Modified Files -- doc/src/sgml/client-auth.sgml |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-

[COMMITTERS] pgsql: Document that multiple LDAP servers can be specified

Document that multiple LDAP servers can be specified Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/589adb86ee826190d2b6e744d117eee1fa6bbf75 Modified Files -- doc/src/sgml/client-auth.sgml |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) --

[COMMITTERS] pgsql: Document that multiple LDAP servers can be specified

Document that multiple LDAP servers can be specified Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff/be5531c58d323b1c154d3c18233aca2c25a1ad89 Modified Files -- doc/src/sgml/client-auth.sgml |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-

[COMMITTERS] pgsql: Document that multiple LDAP servers can be specified

Document that multiple LDAP servers can be specified Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/864c38c59e6c70f18f40881e47dd5f4466dba55f Modified Files -- doc/src/sgml/client-auth.sgml |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-

[COMMITTERS] pgsql: Clean up whitespace and indentation in parser and scanner files

Clean up whitespace and indentation in parser and scanner files These are not touched by pgindent, so clean them up a bit manually. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/654e1f96b0642124fb2996f1b7e64140b2898f14 Modified Files -- contrib/cube/cu

[COMMITTERS] pgsql: Split work of bgwriter between 2 processes: bgwriter and checkpo

Split work of bgwriter between 2 processes: bgwriter and checkpointer. bgwriter is now a much less important process, responsible for page cleaning duties only. checkpointer is now responsible for checkpoints and so has a key role in shutdown. Later patches will correct doc references to the now ol

[COMMITTERS] pgsql: Allow pg_upgrade to upgrade an old cluster that doesn't have a

Allow pg_upgrade to upgrade an old cluster that doesn't have a 'postgres' database. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/a50d860ae1dfca56148dd41692b963bb859bf1d6 Modified Files -- contrib/pg_upgrade/check.c | 37 +---

[COMMITTERS] pgsql: Comment changes to show bgwriter no longer performs checkpoints.

Comment changes to show bgwriter no longer performs checkpoints. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/f3ebaad45b473f3a53de2cd2a5252cd653aa46f3 Modified Files -- src/backend/access/transam/xlog.c |6 +++--- src/backend/commands/dbcommands.c |

[COMMITTERS] pgsql: Update pg_upgrade comment on missing 'postgres' database.

Update pg_upgrade comment on missing 'postgres' database. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/09d1174e5ad3ec7c90c99e2ad4dd896368b018ce Modified Files -- contrib/pg_upgrade/relfilenode.c |3 ++- 1 files changed, 2 insertions(+), 1 deletions(

[COMMITTERS] pgsql: Add new file for checkpointer.c

Add new file for checkpointer.c Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/bf405ba8e460051e715d0a91442b579e590328ce Modified Files -- src/backend/postmaster/checkpointer.c | 1236 + 1 files changed, 1236 insertions(+),

[COMMITTERS] pgsql: Have checkpointer send stats once each processing loop.

Have checkpointer send stats once each processing loop. Noted by Fujii Masao Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/3ba182056faac66012aad8dedf2cb50ba511d989 Modified Files -- src/backend/postmaster/checkpointer.c |5 + 1 files changed, 5

[COMMITTERS] pgsql: Fix race condition with toast table access from a stale syscache

Fix race condition with toast table access from a stale syscache entry. If a tuple in a syscache contains an out-of-line toasted field, and we try to fetch that field shortly after some other transaction has committed an update or deletion of the tuple, there is a race condition: vacuum could come

[COMMITTERS] pgsql: Fix race condition with toast table access from a stale syscache

Fix race condition with toast table access from a stale syscache entry. If a tuple in a syscache contains an out-of-line toasted field, and we try to fetch that field shortly after some other transaction has committed an update or deletion of the tuple, there is a race condition: vacuum could come

[COMMITTERS] pgsql: Fix race condition with toast table access from a stale syscache

Fix race condition with toast table access from a stale syscache entry. If a tuple in a syscache contains an out-of-line toasted field, and we try to fetch that field shortly after some other transaction has committed an update or deletion of the tuple, there is a race condition: vacuum could come

[COMMITTERS] pgsql: Fix race condition with toast table access from a stale syscache

Fix race condition with toast table access from a stale syscache entry. If a tuple in a syscache contains an out-of-line toasted field, and we try to fetch that field shortly after some other transaction has committed an update or deletion of the tuple, there is a race condition: vacuum could come

[COMMITTERS] pgsql: Fix race condition with toast table access from a stale syscache

Fix race condition with toast table access from a stale syscache entry. If a tuple in a syscache contains an out-of-line toasted field, and we try to fetch that field shortly after some other transaction has committed an update or deletion of the tuple, there is a race condition: vacuum could come

[COMMITTERS] pgsql: Fix race condition with toast table access from a stale syscache

Fix race condition with toast table access from a stale syscache entry. If a tuple in a syscache contains an out-of-line toasted field, and we try to fetch that field shortly after some other transaction has committed an update or deletion of the tuple, there is a race condition: vacuum could come

[COMMITTERS] pgsql: Preserve Var location information during flatten_join_alias_vars

Preserve Var location information during flatten_join_alias_vars. This allows us to give correct syntax error pointers when complaining about ungrouped variables in a join query with aggregates or GROUP BY. It's pretty much irrelevant for the planner's use of the function, though perhaps it might

[COMMITTERS] pgsql: Initialize myProcLocks queues just once, at postmaster startup.

Initialize myProcLocks queues just once, at postmaster startup. In assert-enabled builds, we assert during the shutdown sequence that the queues have been properly emptied, and during process startup that we are inheriting empty queues. In non-assert enabled builds, we just save a few cycles. Br