Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension

Hi I am testing it, and output is strange 2015-05-15 11:49:25.046 CEST pavel postgres: LOG: AUDIT: SESSION,1,1,DDL,DROP TABLE,,,drop table foo;, 2015-05-15 11:49:25.046 CEST pavel postgres: STATEMENT: drop table foo; 2015-05-15 11:49:28.291 CEST pavel postgres: LOG: AUDIT: SESSION,2,1,DDL,CREA

Re: [COMMITTERS] pgsql: Separate block sampling functions

On 15 May 2015 at 04:59, Tom Lane wrote: > The difference there was that that was specifically adding a new feature > of value to FDWs. This is just drive-by breakage. > I think that comment is reasonable. I will continue with my commits of tablesample, then return to see if we can improve/rev

Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension

On 15 May 2015 at 10:56, Pavel Stehule wrote: > Hi > > I am testing it, and output is strange > > 2015-05-15 11:49:25.046 CEST pavel postgres: LOG: AUDIT: > SESSION,1,1,DDL,DROP TABLE,,,drop table foo;, > 2015-05-15 11:49:25.046 CEST pavel postgres: STATEMENT: drop table foo; > 2015-05-15 11:49:

Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension

2015-05-15 12:14 GMT+02:00 Thom Brown : > On 15 May 2015 at 10:56, Pavel Stehule wrote: > > Hi > > > > I am testing it, and output is strange > > > > 2015-05-15 11:49:25.046 CEST pavel postgres: LOG: AUDIT: > > SESSION,1,1,DDL,DROP TABLE,,,drop table foo;, > > 2015-05-15 11:49:25.046 CEST pavel

Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension

On 15 May 2015 at 11:20, Pavel Stehule wrote: > > > 2015-05-15 12:14 GMT+02:00 Thom Brown : >> >> On 15 May 2015 at 10:56, Pavel Stehule wrote: >> > Hi >> > >> > I am testing it, and output is strange >> > >> > 2015-05-15 11:49:25.046 CEST pavel postgres: LOG: AUDIT: >> > SESSION,1,1,DDL,DROP TA

Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension

2015-05-15 12:37 GMT+02:00 Thom Brown : > On 15 May 2015 at 11:20, Pavel Stehule wrote: > > > > > > 2015-05-15 12:14 GMT+02:00 Thom Brown : > >> > >> On 15 May 2015 at 10:56, Pavel Stehule wrote: > >> > Hi > >> > > >> > I am testing it, and output is strange > >> > > >> > 2015-05-15 11:49:25.046

Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension

* Thom Brown ([email protected]) wrote: > If it were empty, it would then be indistinguishable from a statement > executed with a single parameter passed as an empty string. NULL, but yes. > Speaking of which, I notice that nulls show up as nothing too. How > does one distinguish between an empty s

[COMMITTERS] pgsql: Support VERBOSE option in REINDEX command.

Support VERBOSE option in REINDEX command. When this option is specified, a progress report is printed as each index is reindexed. Per discussion, we agreed on the following syntax for the extensibility of the options. REINDEX (flexible options) { INDEX | ... } name Sawada Masahiko. Reviewe

[COMMITTERS] pgsql: Allow GiST distance function to return merely a lower-bound.

Allow GiST distance function to return merely a lower-bound. The distance function can now set *recheck = false, like index quals. The executor will then re-check the ORDER BY expressions, and use a queue to reorder the results on the fly. This makes it possible to do kNN-searches on polygons and

Re: [COMMITTERS] pgsql: Separate block sampling functions

On 05/15/2015 06:04 AM, Simon Riggs wrote: On 15 May 2015 at 04:59, Tom Lane > wrote: The difference there was that that was specifically adding a new feature of value to FDWs. This is just drive-by breakage. I think that comment is reasonable. I will c

Re: [COMMITTERS] pgsql: Separate block sampling functions

On Fri, May 15, 2015 at 8:44 PM, Andrew Dunstan wrote: > > On 05/15/2015 06:04 AM, Simon Riggs wrote: >> >> On 15 May 2015 at 04:59, Tom Lane > > wrote: >> >> The difference there was that that was specifically adding a new >> feature >> of value to FDWs. Th

Re: [COMMITTERS] pgsql: Allow GiST distance function to return merely a lower-bound.

On Fri, May 15, 2015 at 8:27 PM, Heikki Linnakangas wrote: > Allow GiST distance function to return merely a lower-bound. > > The distance function can now set *recheck = false, like index quals. The > executor will then re-check the ORDER BY expressions, and use a queue to > reorder the results o

Re: [COMMITTERS] pgsql: Allow GiST distance function to return merely a lower-bound.

On 05/15/2015 03:05 PM, Fujii Masao wrote: Seems this patch causes the regression test of pg_trgm fail. The regression diff that I got is: *** /home/postgres/pgsql/head/contrib/pg_trgm/expected/pg_trgm.out 2013-07-23 16:46:22.212488785 +0900 --- /home/postgres/pgsql/head/contrib/pg_trgm/results/

[COMMITTERS] pgsql: Support --verbose option in reindexdb.

Support --verbose option in reindexdb. Sawada Masahiko, reviewed by Fabrízio Mello Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/458a07701e2e464558238aeb6058b5179b133921 Modified Files -- doc/src/sgml/ref/reindexdb.sgml| 17 - src/bin/

[COMMITTERS] pgsql: Remove useless pg_audit.conf

Remove useless pg_audit.conf No need to have pg_audit.conf any longer since the regression tests are just loading the module at the start of each session (to simulate being in shared_preload_libraries, which isn't something we can actually make happen on the buildfarm itself, it seems). Pointed o

Re: [COMMITTERS] pgsql: Make repeated 'make installcheck' runs work

* Tom Lane ([email protected]) wrote: > Stephen Frost writes: > > Make repeated 'make installcheck' runs work > > Much better, thanks. > > BTW, isn't the pg_audit.conf file useless now? Removed. Thanks! Stephen signature.asc Description: Digital signature

[COMMITTERS] pgsql: Fix insufficiently-paranoid GB18030 encoding verifier.

Fix insufficiently-paranoid GB18030 encoding verifier. The previous coding effectively only verified that the second byte of a multibyte character was in the expected range; moreover, it wasn't careful to make sure that the second byte even exists in the buffer before touching it. The latter seem

[COMMITTERS] pgsql: Fix datatype confusion with the new lossy GiST distance function

Fix datatype confusion with the new lossy GiST distance functions. We can only support a lossy distance function when the distance function's datatype is comparable with the original ordering operator's datatype. The distance function always returns a float8, so we are limited to float8, and float

[COMMITTERS] pgsql: Silence create_index regression test failure.

Silence create_index regression test failure. The expected output contained some floating point values which might get rounded slightly differently on different platforms. The exact output isn't very interesting in this test, so just round it. Per buildfarm member rover_firefly. Branch -- ma

[COMMITTERS] pgsql: docs: consistently uppercase index method and add spacing

docs: consistently uppercase index method and add spacing Consistently uppercase index method names, e.g. GIN, and add space after the index method name and the parentheses enclosing the column names. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/f6d65f0c7068bab6a

[COMMITTERS] pgsql: Add archive_mode='always' option.

Add archive_mode='always' option. In 'always' mode, the standby independently archives all files it receives from the primary. Original patch by Fujii Masao, docs and review by me. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/ffd37740ee6fcd434416ec0c5461f7040e0a1

Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension

On Thu, May 14, 2015 at 11:36 PM, Stephen Frost wrote: > Add pg_audit, an auditing extension > > This extension provides detailed logging classes, ability to control > logging at a per-object level, and includes fully-qualified object > names for logged statements (DML and DDL) in independent fiel

Re: [COMMITTERS] pgsql: Add archive_mode='always' option.

On 05/15/2015 05:55 PM, Heikki Linnakangas wrote: > Add archive_mode='always' option. > > In 'always' mode, the standby independently archives all files it receives > from the primary. > > Original patch by Fujii Masao, docs and review by me. > > Branch > -- > master > > Details > --- >

[COMMITTERS] pgsql: Fix docs build. Oops.

Fix docs build. Oops. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/8b0f105d2d179dc1085b16f0594c8fa78d13267d Modified Files -- doc/src/sgml/high-availability.sgml |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers ma

Re: [COMMITTERS] pgsql: Add archive_mode='always' option.

On 05/15/2015 07:39 PM, Stefan Kaltenbrunner wrote: this broke the docs build: http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=guaibasaurus&dt=2015-05-15%2016%3A17%3A01 Fixed, thanks. - Heikki -- Sent via pgsql-committers mailing list ([email protected]) To make changes to

Re: [COMMITTERS] pgsql: Silence create_index regression test failure.

Heikki Linnakangas writes: > Silence create_index regression test failure. > The expected output contained some floating point values which might get > rounded slightly differently on different platforms. The exact output isn't > very interesting in this test, so just round it. rover_firefly was

[COMMITTERS] pgsql: Fix outdated src/test/mb/ tests, and add a GB18030 test.

Fix outdated src/test/mb/ tests, and add a GB18030 test. The expected-output files for these tests were broken by the recent addition of a warning for hash indexes. Update them. Also add a test case for GB18030 encoding, similar to the other ones. This is a pretty weak test, but it's better than

[COMMITTERS] pgsql: Silence another create_index regression test failure.

Silence another create_index regression test failure. More platform differences in the less-significant digits in output. Per buildfarm member rover_firefly, still. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/11a83bbedd73800db70f6f2af5a8eb10d15d39d7 Modified Fi

Re: [COMMITTERS] pgsql: Silence create_index regression test failure.

On 05/15/2015 08:07 PM, Tom Lane wrote: Heikki Linnakangas writes: Silence create_index regression test failure. The expected output contained some floating point values which might get rounded slightly differently on different platforms. The exact output isn't very interesting in this test, so

[COMMITTERS] pgsql: TABLESAMPLE, SQL Standard and extensible

TABLESAMPLE, SQL Standard and extensible Add a TABLESAMPLE clause to SELECT statements that allows user to specify random BERNOULLI sampling or block level SYSTEM sampling. Implementation allows for extensible sampling functions to be written, using a standard API. Basic version follows SQLStandar

[COMMITTERS] pgsql: doc: CREATE FOREIGN TABLE now allows CHECK ( ... ) NO INHERIT

doc: CREATE FOREIGN TABLE now allows CHECK ( ... ) NO INHERIT Etsuro Fujita Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/92edba2665ae7bf43ed03538311e63652f9e2373 Modified Files -- doc/src/sgml/ref/create_foreign_table.sgml |4 ++-- 1 file changed,

[COMMITTERS] pgsql: Extend GB18030 encoding conversion to cover full Unicode range.

Extend GB18030 encoding conversion to cover full Unicode range. Our previous code for GB18030 <-> UTF8 conversion only covered Unicode code points up to U+, but the actual spec defines conversions for all code points up to U+10. That would be rather impractical as a lookup table, but fort

[COMMITTERS] pgsql: TABLESAMPLE system_rows(limit)

TABLESAMPLE system_rows(limit) Contrib module implementing a tablesample method that allows you to limit the sample by a hard row limit. Petr Jelinek Reviewed by Michael Paquier, Amit Kapila and Simon Riggs Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/9689290ff0

[COMMITTERS] pgsql: TABLESAMPLE system_time(limit)

TABLESAMPLE system_time(limit) Contrib module implementing a tablesample method that allows you to limit the sample by a hard time limit. Petr Jelinek Reviewed by Michael Paquier, Amit Kapila and Simon Riggs Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/149f6f157

[COMMITTERS] pgsql: contrib/tsm_system_rows

contrib/tsm_system_rows Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/4d40494b11883f154e40f3996ad414fb0933bc12 Modified Files -- contrib/tsm_system_rows/.gitignore |4 + contrib/tsm_system_rows/Makefile | 21 ++ ...

[COMMITTERS] pgsql: contrib/tsm_system_time

contrib/tsm_system_time Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/56e121a508a1745c6b0c66ad2f237e9b5f03b19d Modified Files -- contrib/tsm_system_time/.gitignore |4 + contrib/tsm_system_time/Makefile | 21 ++ ...

Re: [COMMITTERS] pgsql: TABLESAMPLE system_time(limit)

On 15 May 2015 at 20:20, Simon Riggs wrote: > TABLESAMPLE system_time(limit) > > Contrib module implementing a tablesample method > that allows you to limit the sample by a hard time > limit. tsm-system-time.sgml (and tsm-system-rows.sgml in the previous commit) appear to be missing. -- Thom

[COMMITTERS] pgsql: Add to contrib/Makefile

Add to contrib/Makefile Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/df259759fbd0a18e8c64f551824a0ec941ba067b Modified Files -- contrib/Makefile |2 ++ 1 file changed, 2 insertions(+) -- Sent via pgsql-committers mailing list (pgsql-committers@po

[COMMITTERS] pgsql: Tablesample method API docs

Tablesample method API docs Petr Jelinek Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/910baf0a96a43a629c3d469b97f31e1f5103ff9e Modified Files -- doc/src/sgml/filelist.sgml |1 + doc/src/sgml/postgres.sgml |1 + doc/src/sgml/t

Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension

Fujii, * Fujii Masao ([email protected]) wrote: > pg_audit uses 1.0.0 as its version number. But, is the third digit really > required? Why? We usually uses the version number with two digits in > contrib modules. I have to admit, I didn't look closely at how we handled versions in contrib mo

[COMMITTERS] pgsql: Fix uninitialized variable.

Fix uninitialized variable. Per compiler warnings. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/66493dd7aa02e19e93f7d5687acaab70075db34f Modified Files -- src/backend/commands/explain.c |1 + 1 file changed, 1 insertion(+) -- Sent via pgsql-comm

[COMMITTERS] pgsql: SQLStandard feature T613 Sampling now Supported

SQLStandard feature T613 Sampling now Supported Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/1e98fa0bf8de9d25d97fb346755a9c9c17bba549 Modified Files -- src/backend/catalog/sql_features.txt |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- S

Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension

Stephen Frost wrote: > * Fujii Masao ([email protected]) wrote: > > CREATE EXTENSION pg_audit failed with the following error message > > when shared_preload_libraries and pg_audit.log are set to pg_audit and > > ddl, respectively. > > > > =# create extension pg_audit ; > > ERROR: pg_event_

[COMMITTERS] pgsql: Move strategy numbers to include/access/stratnum.h

Move strategy numbers to include/access/stratnum.h For upcoming BRIN opclasses, it's convenient to have strategy numbers defined in a single place. Since there's nothing appropriate, create it. The StrategyNumber typedef now lives there, as well as existing strategy numbers for B-trees (from ske

Re: [COMMITTERS] pgsql: contrib/tsm*

It seems two .sgml files are missing (and this prevents the docs from building): tsm-system-rows.sgml, and tsm-system-time.sgml openjade:contrib.sgml:145:1:E: cannot find "tsm-system-rows.sgml"; tried "tsm-system-rows.sgml", "./tsm-system-rows.sgml", "./tsm-system-rows.sgml", "/usr/share/sgml/

Re: [COMMITTERS] pgsql: contrib/tsm_system_time

On Fri, May 15, 2015 at 3:32 PM, Simon Riggs wrote: > contrib/tsm_system_time I don't want to be overly critical here, but I find that a pretty worthless commit message. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-committers ma

[COMMITTERS] pgsql: Improve test for CONVERT() with GB18030 <-> UTF8.

Improve test for CONVERT() with GB18030 <-> UTF8. Add a bit of coverage of high code points. Arjen Nienhuis Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/199f5973c50fe94e128508ff2218c42126fd0ee1 Modified Files -- src/test/regress/expected/conversion.o

[COMMITTERS] pgsql: Add BRIN infrastructure for "inclusion" opclasses

Add BRIN infrastructure for "inclusion" opclasses This lets BRIN be used with R-Tree-like indexing strategies. Also provided are operator classes for range types, box and inet/cidr. The infrastructure provided here should be sufficient to create operator classes for similar datatypes; for instanc

Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension

On 5/15/15 3:44 PM, Stephen Frost wrote: > * Fujii Masao ([email protected]) wrote: >> CREATE EXTENSION pg_audit failed with the following error message >> when shared_preload_libraries and pg_audit.log are set to pg_audit and >> ddl, respectively. >> >> =# create extension pg_audit ; >> ERROR:

Re: [COMMITTERS] pgsql: Add BRIN infrastructure for "inclusion" opclasses

Alvaro Herrera writes: > Add BRIN infrastructure for "inclusion" opclasses sittela thinks there's something wrong with this. Not clear why it'd be getting different results from other critters; Andrew, is there anything unusual about that machine's hardware or config? reg

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2015d.

Update time zone data files to tzdata release 2015d. DST law changes in Egypt, Mongolia, Palestine. Historical corrections for Canada and Chile. Revised zone abbreviation for America/Adak (HST/HDT not HAST/HADT). Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2015d.

Update time zone data files to tzdata release 2015d. DST law changes in Egypt, Mongolia, Palestine. Historical corrections for Canada and Chile. Revised zone abbreviation for America/Adak (HST/HDT not HAST/HADT). Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2015d.

Update time zone data files to tzdata release 2015d. DST law changes in Egypt, Mongolia, Palestine. Historical corrections for Canada and Chile. Revised zone abbreviation for America/Adak (HST/HDT not HAST/HADT). Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/9d366c

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2015d.

Update time zone data files to tzdata release 2015d. DST law changes in Egypt, Mongolia, Palestine. Historical corrections for Canada and Chile. Revised zone abbreviation for America/Adak (HST/HDT not HAST/HADT). Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2015d.

Update time zone data files to tzdata release 2015d. DST law changes in Egypt, Mongolia, Palestine. Historical corrections for Canada and Chile. Revised zone abbreviation for America/Adak (HST/HDT not HAST/HADT). Branch -- REL9_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff

[COMMITTERS] pgsql: Update time zone data files to tzdata release 2015d.

Update time zone data files to tzdata release 2015d. DST law changes in Egypt, Mongolia, Palestine. Historical corrections for Canada and Chile. Revised zone abbreviation for America/Adak (HST/HDT not HAST/HADT). Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff

Re: [COMMITTERS] pgsql: contrib/tsm_system_time

On Sat, May 16, 2015 at 5:28 AM, Robert Haas wrote: > On Fri, May 15, 2015 at 3:32 PM, Simon Riggs wrote: >> contrib/tsm_system_time > > I don't want to be overly critical here, but I find that a pretty > worthless commit message. And there is no documentation. -- Michael -- Sent via pgsql-c

[COMMITTERS] pgsql: Add docs for tablesample system_rows()

Add docs for tablesample system_rows() Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/6e4415c6aa428132dd41c8bf23a0885fca0f2271 Modified Files -- doc/src/sgml/tsm-system-rows.sgml | 50 + 1 file changed, 50 insertions(

Re: [COMMITTERS] pgsql: contrib/tsm_system_time

On 2015-05-16 09:01:18 +0900, Michael Paquier wrote: > And there is no documentation. Which seems to be caused by files accidentally not committed. Thus breaking doc builds. I'll comment out the reference to allow the buildfarm to turn a littlebit greener for a while and test for breakage in other

[COMMITTERS] pgsql: Support GROUPING SETS, CUBE and ROLLUP.

Support GROUPING SETS, CUBE and ROLLUP. This SQL standard functionality allows to aggregate data by different GROUP BY clauses at once. Each grouping set returns rows with columns grouped by in other sets set to NULL. This could previously be achieved by doing each grouping as a separate query, c

[COMMITTERS] pgsql: Add docs for tablesample system_time()

Add docs for tablesample system_time() Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/f941d033296eb99eeac60f22fc70938893bf7a30 Modified Files -- doc/src/sgml/tsm-system-time.sgml | 51 + 1 file changed, 51 insertions(

Re: [COMMITTERS] pgsql: contrib/tsm_system_time

On 16 May 2015 at 02:45, Andres Freund wrote: > On 2015-05-16 09:01:18 +0900, Michael Paquier wrote: > > And there is no documentation. > > Which seems to be caused by files accidentally not committed. Thus > breaking doc builds. I'll comment out the reference to allow the > buildfarm to turn a l

[COMMITTERS] pgsql: Avoid direct use of INFINITY.

Avoid direct use of INFINITY. It's not very portable. Per buildfarm. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/12cc299c65ba6124c7d459f2605404ad43909db3 Modified Files -- src/backend/lib/bipartite_match.c |9 + 1 file changed, 5 insertio

[COMMITTERS] pgsql: pg_upgrade: only allow template0 to be non-connectable

pg_upgrade: only allow template0 to be non-connectable This patch causes pg_upgrade to error out during its check phase if: (1) template0 is marked connectable or (2) any other database is marked non-connectable This is done because, in the first case, pg_upgrade would fail because the pg_dumpa

[COMMITTERS] pgsql: pg_upgrade: only allow template0 to be non-connectable

pg_upgrade: only allow template0 to be non-connectable This patch causes pg_upgrade to error out during its check phase if: (1) template0 is marked connectable or (2) any other database is marked non-connectable This is done because, in the first case, pg_upgrade would fail because the pg_dumpa

[COMMITTERS] pgsql: pg_upgrade: only allow template0 to be non-connectable

pg_upgrade: only allow template0 to be non-connectable This patch causes pg_upgrade to error out during its check phase if: (1) template0 is marked connectable or (2) any other database is marked non-connectable This is done because, in the first case, pg_upgrade would fail because the pg_dumpa

[COMMITTERS] pgsql: pg_upgrade: only allow template0 to be non-connectable

pg_upgrade: only allow template0 to be non-connectable This patch causes pg_upgrade to error out during its check phase if: (1) template0 is marked connectable or (2) any other database is marked non-connectable This is done because, in the first case, pg_upgrade would fail because the pg_dumpa

[COMMITTERS] pgsql: pg_upgrade: only allow template0 to be non-connectable

pg_upgrade: only allow template0 to be non-connectable This patch causes pg_upgrade to error out during its check phase if: (1) template0 is marked connectable or (2) any other database is marked non-connectable This is done because, in the first case, pg_upgrade would fail because the pg_dumpa

[COMMITTERS] pgsql: pg_upgrade: only allow template0 to be non-connectable

pg_upgrade: only allow template0 to be non-connectable This patch causes pg_upgrade to error out during its check phase if: (1) template0 is marked connectable or (2) any other database is marked non-connectable This is done because, in the first case, pg_upgrade would fail because the pg_dumpa

[COMMITTERS] pgsql: pg_upgrade: force timeline 1 in the new cluster

pg_upgrade: force timeline 1 in the new cluster Previously, this prevented promoted standby servers from being upgraded because of a missing WAL history file. (Timeline 1 doesn't need a history file, and we don't copy WAL files anyway.) Report by Christian Echerer(?), Alexey Klyukin Backpatch

[COMMITTERS] pgsql: pg_upgrade: force timeline 1 in the new cluster

pg_upgrade: force timeline 1 in the new cluster Previously, this prevented promoted standby servers from being upgraded because of a missing WAL history file. (Timeline 1 doesn't need a history file, and we don't copy WAL files anyway.) Report by Christian Echerer(?), Alexey Klyukin Backpatch

[COMMITTERS] pgsql: pg_upgrade: force timeline 1 in the new cluster

pg_upgrade: force timeline 1 in the new cluster Previously, this prevented promoted standby servers from being upgraded because of a missing WAL history file. (Timeline 1 doesn't need a history file, and we don't copy WAL files anyway.) Report by Christian Echerer(?), Alexey Klyukin Backpatch

[COMMITTERS] pgsql: pg_upgrade: force timeline 1 in the new cluster

pg_upgrade: force timeline 1 in the new cluster Previously, this prevented promoted standby servers from being upgraded because of a missing WAL history file. (Timeline 1 doesn't need a history file, and we don't copy WAL files anyway.) Report by Christian Echerer(?), Alexey Klyukin Backpatch

[COMMITTERS] pgsql: pg_upgrade: force timeline 1 in the new cluster

pg_upgrade: force timeline 1 in the new cluster Previously, this prevented promoted standby servers from being upgraded because of a missing WAL history file. (Timeline 1 doesn't need a history file, and we don't copy WAL files anyway.) Report by Christian Echerer(?), Alexey Klyukin Backpatch

[COMMITTERS] pgsql: pg_upgrade: force timeline 1 in the new cluster

pg_upgrade: force timeline 1 in the new cluster Previously, this prevented promoted standby servers from being upgraded because of a missing WAL history file. (Timeline 1 doesn't need a history file, and we don't copy WAL files anyway.) Report by Christian Echerer(?), Alexey Klyukin Backpatch

Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension

On Sat, May 16, 2015 at 4:44 AM, Stephen Frost wrote: > Fujii, > > * Fujii Masao ([email protected]) wrote: >> pg_audit uses 1.0.0 as its version number. But, is the third digit really >> required? Why? We usually uses the version number with two digits in >> contrib modules. > > I have to adm