[COMMITTERS] pgsql: Improve pg_upgrade relation name check logic for pre-8.4 servers

Improve pg_upgrade relation name check logic for pre-8.4 servers. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/a54ba23c087a23222a7c76b33c61cddad5278712 Modified Files -- contrib/pg_upgrade/info.c |6 +++--- 1 files changed, 3 insertions(+), 3 deleti

[COMMITTERS] pgsql: Fix incorrect access to pg_index.indcollation.

Fix incorrect access to pg_index.indcollation. Since this field is after a variable-length field, it can't simply be accessed via the C struct for pg_index. Fortunately, the relcache already did the dirty work of pulling the information out to where it can be accessed easily, so this is a one-lin

[COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.

Efficient transaction-controlled synchronous replication. If a standby is broadcasting reply messages and we have named one or more standbys in synchronous_standby_names then allow users who set synchronous_replication to wait for commit, which then provides strict data integrity guarantees. Design

Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.

On 03/06/2011 05:51 PM, Simon Riggs wrote: Efficient transaction-controlled synchronous replication. I'm glad this is in, but I thought we agreed NOT to call it "synchronous replication". cheers andrew -- Sent via pgsql-committers mailing list ([email protected]) To make c

[COMMITTERS] pgsql: Fix pg_dump's dump order for collations versus extensions.

Fix pg_dump's dump order for collations versus extensions. Mixing them together alphabetically won't be nice. Per my gripe of 2011-02-12. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/f24fa9c1a511b24357ea4c1a2be0e70c73adadd7 Modified Files -- src/bin/

Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.

Simon Riggs writes: > Efficient transaction-controlled synchronous replication. This patch broke the build. Kindly fix or revert at once. regards, tom lane -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription:

Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.

On Sun, Mar 6, 2011 at 6:28 PM, Tom Lane wrote: > Simon Riggs writes: >> Efficient transaction-controlled synchronous replication. > > This patch broke the build.  Kindly fix or revert at once. > Seems Simon forgot to include src/include/replication/syncrep.h on the commit -- Jaime Casanova   

Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.

On Sun, Mar 6, 2011 at 6:36 PM, Jaime Casanova wrote: > On Sun, Mar 6, 2011 at 6:28 PM, Tom Lane wrote: >> Simon Riggs writes: >>> Efficient transaction-controlled synchronous replication. >> >> This patch broke the build.  Kindly fix or revert at once. >> > > Seems Simon forgot to include src/i

[COMMITTERS] pgsql: Add new files for syncrep missed in previous commit

Add new files for syncrep missed in previous commit Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/966fb05b588ab33a6c99c6a26308941e1b3a1188 Modified Files -- src/backend/replication/syncrep.c | 589 + src/include/repli

[COMMITTERS] pgsql: Catversion increment for pg_stat_replication changes for syncrep

Catversion increment for pg_stat_replication changes for syncrep Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/dcfe3f60c12880c52fd3cb9b5d51ff44c946dd6c Modified Files -- src/include/catalog/catversion.h |2 +- 1 files changed, 1 insertions(+), 1 dele

Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.

On Sun, 2011-03-06 at 18:28 -0500, Tom Lane wrote: > Simon Riggs writes: > > Efficient transaction-controlled synchronous replication. > > This patch broke the build. Kindly fix or revert at once. I think that's fixed it now. I was in the middle of doing that when your last commit hit, so I had

[COMMITTERS] pgsql: Dynamic array required within pg_stat_replication.

Dynamic array required within pg_stat_replication. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/cae4974e3d4c0cb1237568b55a2cee4482d42f40 Modified Files -- src/backend/replication/walsender.c |4 +++- 1 files changed, 3 insertions(+), 1 deletions(-)

[COMMITTERS] pgsql: Add missing "static" marker to internal_ping().

Add missing "static" marker to internal_ping(). Per testing with a compiler that doesn't like that. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/775464e8450677602833b1d11b919838e7b2b29a Modified Files -- src/interfaces/libpq/fe-connect.c |2 +- 1 f

[COMMITTERS] pgsql: Fix a couple more missing "static" markers.

Fix a couple more missing "static" markers. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/dfe18f18d262df731378cbf38a4136f08ca119a5 Modified Files -- contrib/pg_upgrade/check.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) -- Sent via p

[COMMITTERS] pgsql: Suppress some "variable might be clobbered by longjmp" warnings.

Suppress some "variable might be clobbered by longjmp" warnings. Seen with an older gcc version. I'm not sure these represent any real risk factor, but still a bit scary. Anyway we have lots of other volatile-marked variables in this code, so a couple more won't hurt. Branch -- master Deta

[COMMITTERS] pgsql: Tighten pg_upgrade check for pre-8.4 toast table name matching.

Tighten pg_upgrade check for pre-8.4 toast table name matching. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/05d93c38a791836eeceaf8edb0ea8cb19cdf2760 Modified Files -- contrib/pg_upgrade/info.c |5 +++-- 1 files changed, 3 insertions(+), 2 deletions