Re: [HACKERS] Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold

2016-05-31 Thread Robert Haas
On Fri, May 27, 2016 at 10:58 AM, Kevin Grittner wrote: >> As far as I can see normal index builds will allow concurrent hot >> prunes and everything; since those only require page-level >> exclusive locks. >> >> So for !concurrent builds we might end up with a corrupt index. > > ... by which you

[COMMITTERS] pgsql: Fix typo in CREATE DATABASE syntax synopsis.

2016-05-31 Thread Tom Lane
Fix typo in CREATE DATABASE syntax synopsis. Misplaced "]", evidently a thinko in commit 213335c14. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/6d69ea33180263403f0377e420e4035105ef8627 Modified Files -- doc/src/sgml/ref/create_database.sgml | 4 ++--

[COMMITTERS] pgsql: Fix typo in CREATE DATABASE syntax synopsis.

2016-05-31 Thread Tom Lane
Fix typo in CREATE DATABASE syntax synopsis. Misplaced "]", evidently a thinko in commit 213335c14. Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/ad829c307b5b4f466adf760b1a209840900ec2a5 Modified Files -- doc/src/sgml/ref/create_database.sgml |

Re: [HACKERS] Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold

2016-05-31 Thread Kevin Grittner
On Tue, May 31, 2016 at 10:03 AM, Robert Haas wrote: > On Fri, May 27, 2016 at 10:58 AM, Kevin Grittner wrote: >>> As far as I can see normal index builds will allow concurrent hot >>> prunes and everything; since those only require page-level >>> exclusive locks. >>> >>> So for !concurrent build

[COMMITTERS] pgsql: Fix whitespace

2016-05-31 Thread Peter Eisentraut
Fix whitespace Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/aa14bc41d1b139fc7b8b3cdd23e422fad86a9b9b Modified Files -- doc/src/sgml/bloom.sgml| 6 +++--- doc/src/sgml/fdwhandler.sgml | 2 +- doc/src/sgml/gin.sgml | 2 +-

[COMMITTERS] pgsql: Avoid useless closely-spaced writes of statistics files.

2016-05-31 Thread Tom Lane
Avoid useless closely-spaced writes of statistics files. The original intent in the stats collector was that we should not write out stats data oftener than every PGSTAT_STAT_INTERVAL msec. Backends will not make requests at all if they see the existing data is newer than that, and the stats coll

[COMMITTERS] pgsql: Avoid useless closely-spaced writes of statistics files.

2016-05-31 Thread Tom Lane
Avoid useless closely-spaced writes of statistics files. The original intent in the stats collector was that we should not write out stats data oftener than every PGSTAT_STAT_INTERVAL msec. Backends will not make requests at all if they see the existing data is newer than that, and the stats coll

[COMMITTERS] pgsql: Avoid useless closely-spaced writes of statistics files.

2016-05-31 Thread Tom Lane
Avoid useless closely-spaced writes of statistics files. The original intent in the stats collector was that we should not write out stats data oftener than every PGSTAT_STAT_INTERVAL msec. Backends will not make requests at all if they see the existing data is newer than that, and the stats coll

[COMMITTERS] pgsql: Avoid useless closely-spaced writes of statistics files.

2016-05-31 Thread Tom Lane
Avoid useless closely-spaced writes of statistics files. The original intent in the stats collector was that we should not write out stats data oftener than every PGSTAT_STAT_INTERVAL msec. Backends will not make requests at all if they see the existing data is newer than that, and the stats coll

[COMMITTERS] pgsql: doc: Update version() and current_date output in tutorial

2016-05-31 Thread Peter Eisentraut
doc: Update version() and current_date output in tutorial While the version number is automatically updated in the example output, the other details looked a bit dated. suggested by [email protected] Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/9ee56dfeee