[COMMITTERS] pgsql: Fix psql crash while parsing SQL file whose encoding is differen
Fix psql crash while parsing SQL file whose encoding is different from client encoding and the client encoding is not *safe* one. Such an example is, file encoding is UTF-8 and client encoding SJIS. Patch contributed by Jiang Guiqing. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/53edb8dc0274e0d05eb0371ce84b7fb14cb5eb5a Modified Files -- src/bin/psql/psqlscan.l |2 +- 1 files changed, 1 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: Fix psql crash while parsing SQL file whose encoding is differen
Fix psql crash while parsing SQL file whose encoding is different from client encoding and the client encoding is not *safe* one. Such an example is, file encoding is UTF-8 and client encoding SJIS. Patch contributed by Jiang Guiqing. Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/a7c53092d88bf9c617713389bc11f0670762b723 Modified Files -- src/bin/psql/psqlscan.l |2 +- 1 files changed, 1 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: Fix psql crash while parsing SQL file whose encoding is differen
Fix psql crash while parsing SQL file whose encoding is different from client encoding and the client encoding is not *safe* one. Such an example is, file encoding is UTF-8 and client encoding SJIS. Patch contributed by Jiang Guiqing. Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff/ceee108acdf4c1f962574b3f9f9a6999891771dd Modified Files -- src/bin/psql/psqlscan.l |2 +- 1 files changed, 1 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: Fix psql crash while parsing SQL file whose encoding is differen
Fix psql crash while parsing SQL file whose encoding is different from client encoding and the client encoding is not *safe* one. Such an example is, file encoding is UTF-8 and client encoding SJIS. Patch contributed by Jiang Guiqing. Branch -- REL8_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/cd99d20550a36c673cc5003c7987f816d6cd3eb3 Modified Files -- src/bin/psql/psqlscan.l |2 +- 1 files changed, 1 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: Fix psql crash while parsing SQL file whose encoding is differen
Fix psql crash while parsing SQL file whose encoding is different from client encoding and the client encoding is not *safe* one. Such an example is, file encoding is UTF-8 and client encoding SJIS. Patch contributed by Jiang Guiqing. Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/530cbf6b10af156276d45687d14ca05cd4e39d16 Modified Files -- src/bin/psql/psqlscan.l |2 +- 1 files changed, 1 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: Fix psql crash while parsing SQL file whose encoding is differen
Fix psql crash while parsing SQL file whose encoding is different from client encoding and the client encoding is not *safe* one. Such an example is, file encoding is UTF-8 and client encoding SJIS. Patch contributed by Jiang Guiqing. Branch -- REL8_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/eb851c998d2a37a6512a26dba11a303babe6316a Modified Files -- src/bin/psql/psqlscan.l |2 +- 1 files changed, 1 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: Clarify operation of online checkpoints.
Clarify operation of online checkpoints. Previous comments left, but were too obscure for such an important aspect of the system. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/9f98704b8229f75fb6ec6e379c23cfea51a8f1e4 Modified Files -- src/backend/access/transam/xlog.c | 12 1 files changed, 12 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: XidEpoch++ if wraparound during checkpoint.
XidEpoch++ if wraparound during checkpoint. If wal_level = hot_standby we update the checkpoint nextxid, though in the case where a wraparound occurred half-way through a checkpoint we would neglect updating the epoch also. Updating the nextxid is arguably the wrong thing to do, but changing that may introduce subtle bugs into hot standby startup, while updating the value doesn't cause any known bugs yet. Minimal fix now to HEAD and backbranches, wider fix later in HEAD. Bug reported in #6291 by Daniel Farina and slightly differently in Cause analysis and recommended fixes from Tom Lane and Andres Freund. Applied patch is minimal version of Andres Freund's work. Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/c3f64adef829ea41d3761822b8a043aec3d651f2 Modified Files -- src/backend/access/transam/xlog.c |9 - 1 files changed, 8 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: XidEpoch++ if wraparound during checkpoint.
XidEpoch++ if wraparound during checkpoint. If wal_level = hot_standby we update the checkpoint nextxid, though in the case where a wraparound occurred half-way through a checkpoint we would neglect updating the epoch also. Updating the nextxid is arguably the wrong thing to do, but changing that may introduce subtle bugs into hot standby startup, while updating the value doesn't cause any known bugs yet. Minimal fix now to HEAD and backbranches, wider fix later in HEAD. Bug reported in #6291 by Daniel Farina and slightly differently in Cause analysis and recommended fixes from Tom Lane and Andres Freund. Applied patch is minimal version of Andres Freund's work. Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff/069aa395c0a2d4f73944f13d1bbc15d6106e2277 Modified Files -- src/backend/access/transam/xlog.c |9 - 1 files changed, 8 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: XidEpoch++ if wraparound during checkpoint.
XidEpoch++ if wraparound during checkpoint. If wal_level = hot_standby we update the checkpoint nextxid, though in the case where a wraparound occurred half-way through a checkpoint we would neglect updating the epoch also. Updating the nextxid is arguably the wrong thing to do, but changing that may introduce subtle bugs into hot standby startup, while updating the value doesn't cause any known bugs yet. Minimal fix now to HEAD and backbranches, wider fix later in HEAD. Bug reported in #6291 by Daniel Farina and slightly differently in Cause analysis and recommended fixes from Tom Lane and Andres Freund. Applied patch is minimal version of Andres Freund's work. Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/973c011639e1aecf7256de07e2aa8520f9b49035 Modified Files -- src/backend/access/transam/xlog.c |9 - 1 files changed, 8 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: XidEpoch++ if wraparound during checkpoint.
XidEpoch++ if wraparound during checkpoint. If wal_level = hot_standby we update the checkpoint nextxid, though in the case where a wraparound occurred half-way through a checkpoint we would neglect updating the epoch also. Updating the nextxid is arguably the wrong thing to do, but changing that may introduce subtle bugs into hot standby startup, while updating the value doesn't cause any known bugs yet. Minimal fix now to HEAD and backbranches, wider fix later in HEAD. Bug reported in #6291 by Daniel Farina and slightly differently in Cause analysis and recommended fixes from Tom Lane and Andres Freund. Applied patch is minimal version of Andres Freund's work. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/c11130690d6dca64267201a169cfb38c1adec5ef Modified Files -- src/backend/access/transam/xlog.c |9 - 1 files changed, 8 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: Rearrange storage of data in xl_running_xacts.
Rearrange storage of data in xl_running_xacts. Previously we stored all xids mixed together. Now we store top-level xids first, followed by all subxids. Also skip logging any subxids if the snapshot is suboverflowed, since there are potentially large numbers of them and they are not useful in that case anyway. Has value in the envisaged design for decoding of WAL. No planned effect on Hot Standby. Andres Freund, reviewed by me Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/5c11725867ac3cb06db065f7940143114280649c Modified Files -- src/backend/access/transam/xlog.c |2 + src/backend/storage/ipc/procarray.c | 65 +++ src/backend/storage/ipc/standby.c |8 +++-- src/include/storage/standby.h |2 + 4 files changed, 52 insertions(+), 25 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Don't advance checkPoint.nextXid near the end of a checkpoint se
Don't advance checkPoint.nextXid near the end of a checkpoint sequence. This reverts commit c11130690d6dca64267201a169cfb38c1adec5ef in favor of actually fixing the problem: namely, that we should never have been modifying the checkpoint record's nextXid at this point to begin with. The nextXid should match the state as of the checkpoint's logical WAL position (ie the redo point), not the state as of its physical position. It's especially bogus to advance it in some wal_levels and not others. In any case there is no need for the checkpoint record to carry the same nextXid shown in the XLOG_RUNNING_XACTS record just emitted by LogStandbySnapshot, as any replay operation will already have adopted that value as current. This fixes bug #7710 from Tarvi Pillessaar, and probably also explains bug #6291 from Daniel Farina, in that if a checkpoint were in progress at the instant of XID wraparound, the epoch bump would be lost as reported. (And, of course, these days there's at least a 50-50 chance of a checkpoint being in progress at any given instant.) Diagnosed by me and independently by Andres Freund. Back-patch to all branches supporting hot standby. Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/aaceb0d6acce900144c147fca3d682c11c6adf0c Modified Files -- src/backend/access/transam/xlog.c | 11 +-- src/backend/storage/ipc/standby.c |4 +--- src/include/storage/standby.h |2 +- 3 files changed, 3 insertions(+), 14 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Don't advance checkPoint.nextXid near the end of a checkpoint se
Don't advance checkPoint.nextXid near the end of a checkpoint sequence. This reverts commit c11130690d6dca64267201a169cfb38c1adec5ef in favor of actually fixing the problem: namely, that we should never have been modifying the checkpoint record's nextXid at this point to begin with. The nextXid should match the state as of the checkpoint's logical WAL position (ie the redo point), not the state as of its physical position. It's especially bogus to advance it in some wal_levels and not others. In any case there is no need for the checkpoint record to carry the same nextXid shown in the XLOG_RUNNING_XACTS record just emitted by LogStandbySnapshot, as any replay operation will already have adopted that value as current. This fixes bug #7710 from Tarvi Pillessaar, and probably also explains bug #6291 from Daniel Farina, in that if a checkpoint were in progress at the instant of XID wraparound, the epoch bump would be lost as reported. (And, of course, these days there's at least a 50-50 chance of a checkpoint being in progress at any given instant.) Diagnosed by me and independently by Andres Freund. Back-patch to all branches supporting hot standby. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/3114cb60a1a3f482724adaed4ca17572c5e6bde7 Modified Files -- src/backend/access/transam/xlog.c | 11 +-- src/backend/storage/ipc/standby.c |4 +--- src/include/storage/standby.h |2 +- 3 files changed, 3 insertions(+), 14 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Don't advance checkPoint.nextXid near the end of a checkpoint se
Don't advance checkPoint.nextXid near the end of a checkpoint sequence. This reverts commit c11130690d6dca64267201a169cfb38c1adec5ef in favor of actually fixing the problem: namely, that we should never have been modifying the checkpoint record's nextXid at this point to begin with. The nextXid should match the state as of the checkpoint's logical WAL position (ie the redo point), not the state as of its physical position. It's especially bogus to advance it in some wal_levels and not others. In any case there is no need for the checkpoint record to carry the same nextXid shown in the XLOG_RUNNING_XACTS record just emitted by LogStandbySnapshot, as any replay operation will already have adopted that value as current. This fixes bug #7710 from Tarvi Pillessaar, and probably also explains bug #6291 from Daniel Farina, in that if a checkpoint were in progress at the instant of XID wraparound, the epoch bump would be lost as reported. (And, of course, these days there's at least a 50-50 chance of a checkpoint being in progress at any given instant.) Diagnosed by me and independently by Andres Freund. Back-patch to all branches supporting hot standby. Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff/135f4f605517deb97fed60811ebca32ff94a8488 Modified Files -- src/backend/access/transam/xlog.c | 11 +-- src/backend/storage/ipc/standby.c |4 +--- src/include/storage/standby.h |2 +- 3 files changed, 3 insertions(+), 14 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Don't advance checkPoint.nextXid near the end of a checkpoint se
Don't advance checkPoint.nextXid near the end of a checkpoint sequence. This reverts commit c11130690d6dca64267201a169cfb38c1adec5ef in favor of actually fixing the problem: namely, that we should never have been modifying the checkpoint record's nextXid at this point to begin with. The nextXid should match the state as of the checkpoint's logical WAL position (ie the redo point), not the state as of its physical position. It's especially bogus to advance it in some wal_levels and not others. In any case there is no need for the checkpoint record to carry the same nextXid shown in the XLOG_RUNNING_XACTS record just emitted by LogStandbySnapshot, as any replay operation will already have adopted that value as current. This fixes bug #7710 from Tarvi Pillessaar, and probably also explains bug #6291 from Daniel Farina, in that if a checkpoint were in progress at the instant of XID wraparound, the epoch bump would be lost as reported. (And, of course, these days there's at least a 50-50 chance of a checkpoint being in progress at any given instant.) Diagnosed by me and independently by Andres Freund. Back-patch to all branches supporting hot standby. Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/d08fd1f849ba7419b79094e6cf863b6c190784b5 Modified Files -- src/backend/access/transam/xlog.c | 11 +-- src/backend/storage/ipc/standby.c |4 +--- src/include/storage/standby.h |2 +- 3 files changed, 3 insertions(+), 14 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Reduce scope of changes for COPY FREEZE.
Reduce scope of changes for COPY FREEZE. Allow support only for freezing tuples by explicit command. Previous coding mistakenly extended slightly beyond what was agreed as correct on -hackers. So essentially a partial revoke of earlier work, leaving just the COPY FREEZE command. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/5457a130d3a66db807d1e0ee2b8e829321809b83 Modified Files -- src/backend/access/heap/heapam.c| 13 +++- src/backend/commands/copy.c |9 ++--- src/include/access/heapam.h |3 +- src/test/regress/expected/copy2.out | 60 +- src/test/regress/sql/copy2.sql | 19 ++- 5 files changed, 57 insertions(+), 47 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Recommend triggers, not rules, in the CREATE VIEW reference page
Recommend triggers, not rules, in the CREATE VIEW reference page. We've generally recommended use of INSTEAD triggers over rules since that feature was added; but this old text in the CREATE VIEW reference page didn't get the memo. Noted by Thomas Kellerer. Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/7e487c1b0acbb26a481e64570dcbfe39b3e54abb Modified Files -- doc/src/sgml/ref/create_view.sgml |7 +-- 1 files changed, 5 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Recommend triggers, not rules, in the CREATE VIEW reference page
Recommend triggers, not rules, in the CREATE VIEW reference page. We've generally recommended use of INSTEAD triggers over rules since that feature was added; but this old text in the CREATE VIEW reference page didn't get the memo. Noted by Thomas Kellerer. Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/f7968554ab20e18a78f8e21bda9ff8445f81773f Modified Files -- doc/src/sgml/ref/create_view.sgml |7 +-- 1 files changed, 5 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Recommend triggers, not rules, in the CREATE VIEW reference page
Recommend triggers, not rules, in the CREATE VIEW reference page. We've generally recommended use of INSTEAD triggers over rules since that feature was added; but this old text in the CREATE VIEW reference page didn't get the memo. Noted by Thomas Kellerer. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/d8262b6c9b9dabee397b30f9af3c01d17e8eced8 Modified Files -- doc/src/sgml/ref/create_view.sgml |7 +-- 1 files changed, 5 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update time zone data files to tzdata release 2012j.
Update time zone data files to tzdata release 2012j. DST law changes in Cuba, Israel, Jordan, Libya, Palestine, Western Samoa, and portions of Brazil. Branch -- REL8_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/150c26ad57955e008f7db120d24caaef527584c9 Modified Files -- src/timezone/data/africa | 28 ++-- src/timezone/data/asia | 96 ++- src/timezone/data/australasia | 23 - src/timezone/data/europe |2 +- src/timezone/data/northamerica | 11 - src/timezone/data/southamerica | 17 ++- 6 files changed, 121 insertions(+), 56 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update time zone data files to tzdata release 2012j.
Update time zone data files to tzdata release 2012j. DST law changes in Cuba, Israel, Jordan, Libya, Palestine, Western Samoa, and portions of Brazil. Branch -- REL8_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/628a0c7e5e6bb5369eaf99e9759dbfc8be48dc33 Modified Files -- src/timezone/data/africa | 28 ++-- src/timezone/data/asia | 96 ++- src/timezone/data/australasia | 23 - src/timezone/data/europe |2 +- src/timezone/data/northamerica | 11 - src/timezone/data/southamerica | 17 ++- 6 files changed, 121 insertions(+), 56 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update time zone data files to tzdata release 2012j.
Update time zone data files to tzdata release 2012j. DST law changes in Cuba, Israel, Jordan, Libya, Palestine, Western Samoa, and portions of Brazil. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/fc75d4f81c1b2f27d1954c4b9aac29370c00a0c8 Modified Files -- src/timezone/data/africa | 28 ++-- src/timezone/data/asia | 96 ++- src/timezone/data/australasia | 23 - src/timezone/data/europe |2 +- src/timezone/data/northamerica | 11 - src/timezone/data/southamerica | 17 ++- 6 files changed, 121 insertions(+), 56 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update time zone data files to tzdata release 2012j.
Update time zone data files to tzdata release 2012j. DST law changes in Cuba, Israel, Jordan, Libya, Palestine, Western Samoa, and portions of Brazil. Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff/194bb37ebac43c5b5782dd32bcf45c64434a172d Modified Files -- src/timezone/data/africa | 28 ++-- src/timezone/data/asia | 96 ++- src/timezone/data/australasia | 23 - src/timezone/data/europe |2 +- src/timezone/data/northamerica | 11 - src/timezone/data/southamerica | 17 ++- 6 files changed, 121 insertions(+), 56 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update time zone data files to tzdata release 2012j.
Update time zone data files to tzdata release 2012j. DST law changes in Cuba, Israel, Jordan, Libya, Palestine, Western Samoa, and portions of Brazil. Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/842cb63fd3ca3f5371406b5a1cdffb3a9ec6853a Modified Files -- src/timezone/data/africa | 28 ++-- src/timezone/data/asia | 96 ++- src/timezone/data/australasia | 23 - src/timezone/data/europe |2 +- src/timezone/data/northamerica | 11 - src/timezone/data/southamerica | 17 ++- 6 files changed, 121 insertions(+), 56 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update time zone data files to tzdata release 2012j.
Update time zone data files to tzdata release 2012j. DST law changes in Cuba, Israel, Jordan, Libya, Palestine, Western Samoa, and portions of Brazil. Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/31ab8936c770545d6aaa09d348661ce175f9b33d Modified Files -- src/timezone/data/africa | 28 ++-- src/timezone/data/asia | 96 ++- src/timezone/data/australasia | 23 - src/timezone/data/europe |2 +- src/timezone/data/northamerica | 11 - src/timezone/data/southamerica | 17 ++- 6 files changed, 121 insertions(+), 56 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 mode where contrib installcheck runs each module in a separa
Add mode where contrib installcheck runs each module in a separately named database. Normally each module is tested in aq database named contrib_regression, which is dropped and recreated at the beginhning of each pg_regress run. This mode, enabled by adding USE_MODULE_DB=1 to the make command line, runs most modules in a database with the module name embedded in it. This will make testing pg_upgrade on clusters with the contrib modules a lot easier. Still to be done: adapt to the MSVC build system. Backpatch to 9.0, which is the earliest version it is reasonably possible to test upgrading from. Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff/c8f666abde2af3060af41afe4b03ced2f62d94a9 Modified Files -- contrib/dblink/Makefile |3 +++ src/Makefile.global.in |9 + src/makefiles/pgxs.mk |6 +- 3 files changed, 17 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: Add mode where contrib installcheck runs each module in a separa
Add mode where contrib installcheck runs each module in a separately named database. Normally each module is tested in aq database named contrib_regression, which is dropped and recreated at the beginhning of each pg_regress run. This mode, enabled by adding USE_MODULE_DB=1 to the make command line, runs most modules in a database with the module name embedded in it. This will make testing pg_upgrade on clusters with the contrib modules a lot easier. Still to be done: adapt to the MSVC build system. Backpatch to 9.0, which is the earliest version it is reasonably possible to test upgrading from. Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/513e546a6e75b0a79c3102ce22c583ccd1053ac6 Modified Files -- contrib/dblink/Makefile |3 +++ src/Makefile.global.in |9 + src/makefiles/pgxs.mk |6 +- 3 files changed, 17 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: Add mode where contrib installcheck runs each module in a separa
Add mode where contrib installcheck runs each module in a separately named database. Normally each module is tested in aq database named contrib_regression, which is dropped and recreated at the beginhning of each pg_regress run. This mode, enabled by adding USE_MODULE_DB=1 to the make command line, runs most modules in a database with the module name embedded in it. This will make testing pg_upgrade on clusters with the contrib modules a lot easier. Still to be done: adapt to the MSVC build system. Backpatch to 9.0, which is the earliest version it is reasonably possible to test upgrading from. Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/30248be9635e844918c2873ae7bb598f8a487e49 Modified Files -- contrib/dblink/Makefile |3 +++ src/Makefile.global.in |9 + src/makefiles/pgxs.mk |6 +- 3 files changed, 17 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: Add mode where contrib installcheck runs each module in a separa
Add mode where contrib installcheck runs each module in a separately named database. Normally each module is tested in aq database named contrib_regression, which is dropped and recreated at the beginhning of each pg_regress run. This mode, enabled by adding USE_MODULE_DB=1 to the make command line, runs most modules in a database with the module name embedded in it. This will make testing pg_upgrade on clusters with the contrib modules a lot easier. Still to be done: adapt to the MSVC build system. Backpatch to 9.0, which is the earliest version it is reasonably possible to test upgrading from. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/e2b3c21b05c78c3a726b189242e41d4aa4422bf1 Modified Files -- contrib/dblink/Makefile |3 +++ src/Makefile.global.in |9 + src/makefiles/pgxs.mk |6 +- 3 files changed, 17 insertions(+), 1 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
