[COMMITTERS] pgsql: fe-misc.c depends on pg_config_paths.h

2012-02-06 Thread Alvaro Herrera
fe-misc.c depends on pg_config_paths.h Declare this in Makefile to avoid failures in parallel compiles. Author: Lionel Elie Mamane Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/0c88086df3f79ff48d09440d96be17f3307017ed Modified Files -- src/interfaces/

[COMMITTERS] pgsql: fe-misc.c depends on pg_config_paths.h

2012-02-06 Thread Alvaro Herrera
fe-misc.c depends on pg_config_paths.h Declare this in Makefile to avoid failures in parallel compiles. Author: Lionel Elie Mamane Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff/94c5aa639e7ee75eb271c320f4e592ef5b10b3b1 Modified Files -- src/inte

[COMMITTERS] pgsql: fe-misc.c depends on pg_config_paths.h

2012-02-06 Thread Alvaro Herrera
fe-misc.c depends on pg_config_paths.h Declare this in Makefile to avoid failures in parallel compiles. Author: Lionel Elie Mamane Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/2a846719090eff235ac8dd7815e51859e834331d Modified Files -- src/inte

[COMMITTERS] pgsql: Remove dead declaration.

2012-02-06 Thread Robert Haas
Remove dead declaration. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/96abd81744a90511b7cae9299e589412ce1897c9 Modified Files -- src/bin/pg_dump/pg_backup_archiver.h |1 - 1 files changed, 0 insertions(+), 1 deletions(-) -- Sent via pgsql-committ

[COMMITTERS] pgsql: Add locking around WAL-replay modification of shared-memory vari

2012-02-06 Thread Tom Lane
Add locking around WAL-replay modification of shared-memory variables. Originally, most of this code assumed that no Postgres backends could be running concurrently with it, and so no locking could be needed. That assumption fails in Hot Standby. While it's still true that Hot Standby backends s

[COMMITTERS] pgsql: pg_dump: Reduce dependencies on global variables.

2012-02-06 Thread Robert Haas
pg_dump: Reduce dependencies on global variables. Change various places in the code that are referencing the global Archive object g_fout to instead reference the Archive object fout which is already being passed as a parameter. For parallel pg_dump to work, we're going to need multiple Archive(H

[COMMITTERS] pgsql: Avoid problems with OID wraparound during WAL replay.

2012-02-06 Thread Tom Lane
Avoid problems with OID wraparound during WAL replay. Fix a longstanding thinko in replay of NEXTOID and checkpoint records: we tried to advance nextOid only if it was behind the value in the WAL record, but the comparison would draw the wrong conclusion if OID wraparound had occurred since the pr

[COMMITTERS] pgsql: Avoid problems with OID wraparound during WAL replay.

2012-02-06 Thread Tom Lane
Avoid problems with OID wraparound during WAL replay. Fix a longstanding thinko in replay of NEXTOID and checkpoint records: we tried to advance nextOid only if it was behind the value in the WAL record, but the comparison would draw the wrong conclusion if OID wraparound had occurred since the pr

[COMMITTERS] pgsql: Avoid problems with OID wraparound during WAL replay.

2012-02-06 Thread Tom Lane
Avoid problems with OID wraparound during WAL replay. Fix a longstanding thinko in replay of NEXTOID and checkpoint records: we tried to advance nextOid only if it was behind the value in the WAL record, but the comparison would draw the wrong conclusion if OID wraparound had occurred since the pr

[COMMITTERS] pgsql: Avoid problems with OID wraparound during WAL replay.

2012-02-06 Thread Tom Lane
Avoid problems with OID wraparound during WAL replay. Fix a longstanding thinko in replay of NEXTOID and checkpoint records: we tried to advance nextOid only if it was behind the value in the WAL record, but the comparison would draw the wrong conclusion if OID wraparound had occurred since the pr

[COMMITTERS] pgsql: pg_dump: Remove global Archive pointer.

2012-02-06 Thread Robert Haas
pg_dump: Remove global Archive pointer. Instead, everything that needs the Archive object now gets it as a parameter. This is necessary infrastructure for parallel pg_dump, but is also amply justified by the ugliness of the current code (though a lot more than this is needed to fix that problem).

[COMMITTERS] pgsql: Avoid throwing ERROR during WAL replay of DROP TABLESPACE.

2012-02-06 Thread Tom Lane
Avoid throwing ERROR during WAL replay of DROP TABLESPACE. Although we will not even issue an XLOG_TBLSPC_DROP WAL record unless removal of the tablespace's directories succeeds, that does not guarantee that the same operation will succeed during WAL replay. Foreseeable reasons for it to fail inc

[COMMITTERS] pgsql: Avoid throwing ERROR during WAL replay of DROP TABLESPACE.

2012-02-06 Thread Tom Lane
Avoid throwing ERROR during WAL replay of DROP TABLESPACE. Although we will not even issue an XLOG_TBLSPC_DROP WAL record unless removal of the tablespace's directories succeeds, that does not guarantee that the same operation will succeed during WAL replay. Foreseeable reasons for it to fail inc

[COMMITTERS] pgsql: Avoid throwing ERROR during WAL replay of DROP TABLESPACE.

2012-02-06 Thread Tom Lane
Avoid throwing ERROR during WAL replay of DROP TABLESPACE. Although we will not even issue an XLOG_TBLSPC_DROP WAL record unless removal of the tablespace's directories succeeds, that does not guarantee that the same operation will succeed during WAL replay. Foreseeable reasons for it to fail inc

[COMMITTERS] pgsql: Allow the connection keyword array to carry all seven items in e

2012-02-06 Thread Michael Meskes
Allow the connection keyword array to carry all seven items in ecpglib. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/0ee23b53beb851d60c0eff9bde8fd7a303270720 Modified Files -- src/interfaces/ecpg/ecpglib/connect.c |2 +- 1 files changed, 1 insertion

[COMMITTERS] pgsql: Fix postmaster to attempt restart after a hot-standby crash.

2012-02-06 Thread Tom Lane
Fix postmaster to attempt restart after a hot-standby crash. The postmaster was coded to treat any unexpected exit of the startup process (i.e., the WAL replay process) as a catastrophic crash, and not try to restart it. This was OK so long as the startup process could not have any sibling postmas

[COMMITTERS] pgsql: Fix postmaster to attempt restart after a hot-standby crash.

2012-02-06 Thread Tom Lane
Fix postmaster to attempt restart after a hot-standby crash. The postmaster was coded to treat any unexpected exit of the startup process (i.e., the WAL replay process) as a catastrophic crash, and not try to restart it. This was OK so long as the startup process could not have any sibling postmas

[COMMITTERS] pgsql: Fix postmaster to attempt restart after a hot-standby crash.

2012-02-06 Thread Tom Lane
Fix postmaster to attempt restart after a hot-standby crash. The postmaster was coded to treat any unexpected exit of the startup process (i.e., the WAL replay process) as a catastrophic crash, and not try to restart it. This was OK so long as the startup process could not have any sibling postmas