pgsql: doc: Update for Unix-domain sockets on Windows

2020-04-01 Thread Peter Eisentraut
doc: Update for Unix-domain sockets on Windows Update the documentation to reflect that Unix-domain sockets are now usable on Windows. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/580a446c21f83bcddbaf3ce5f1bab72239c11eb6 Modified Files -- doc/src/sgm

pgsql: Add some comments to some SQL features

2020-04-01 Thread Peter Eisentraut
Add some comments to some SQL features Otherwise, it could be confusing to a reader that some of these well-publicized features are simply listed as unsupported without further explanation. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/c6e0edad465e3774401b7f09ad70

Re: pgsql: doc: add namespace column to pg_buffercache example query

2020-04-01 Thread Peter Eisentraut
On 2020-03-31 23:16, Bruce Momjian wrote: doc: add namespace column to pg_buffercache example query Without the namespace, the table name could be ambiguous. Reported-by: adun...@arbormetrix.com Discussion: https://postgr.es/m/158155175140.23798.2189464781144503...@wrigleys.postgresql.org B

Re: pgsql: doc: adjust UPDATE/DELETE's FROM/USING to match SELECT's FROM

2020-04-01 Thread Peter Eisentraut
On 2020-03-31 22:31, Bruce Momjian wrote: doc: adjust UPDATE/DELETE's FROM/USING to match SELECT's FROM Previously the syntax and wording were unclear. @@ -23,7 +23,7 @@ PostgreSQL documentation [ WITH [ RECURSIVE ] class="parameter">with_query [, ...] ] DELETE FROM [ ONLY ] class="PARAMET

Re: pgsql: doc: clarify hierarchy of objects: global, db, schema, etc.

2020-04-01 Thread Peter Eisentraut
On 2020-04-01 00:10, Bruce Momjian wrote: doc: clarify hierarchy of objects: global, db, schema, etc. The previous wording was confusing because it wasn't in decreasing order and had to backtrack. Also clarify role/user wording. Reported-by: jb...@nuna.com Discussion: https://postgr.es/m/1

pgsql: Add maintenance_io_concurrency to postgresql.conf.sample.

2020-04-01 Thread Thomas Munro
Add maintenance_io_concurrency to postgresql.conf.sample. New GUC from commit fc34b0d9. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/37b3794dfcfb9d55f7ea83693f50b1484caab21c Modified Files -- src/backend/utils/misc/postgresql.conf.sample | 1 + 1 file

pgsql: Allow parallel vacuum to accumulate buffer usage.

2020-04-01 Thread Amit Kapila
Allow parallel vacuum to accumulate buffer usage. Commit 40d964ec99 allowed vacuum command to process indexes in parallel but forgot to accumulate the buffer usage stats of parallel workers. This allows leader backend to accumulate buffer usage stats of all the parallel workers. Reported-by: Jul

pgsql: Allow pg_stat_statements to track planning statistics.

2020-04-01 Thread Fujii Masao
Allow pg_stat_statements to track planning statistics. This commit makes pg_stat_statements support new GUC pg_stat_statements.track_planning. If this option is enabled, pg_stat_statements tracks the planning statistics of the statements, e.g., the number of times the statement was planned, the to

Re: pgsql: Allow vacuum command to process indexes in parallel.

2020-04-01 Thread Amit Kapila
On Wed, Apr 1, 2020 at 8:39 AM Mahendra Singh Thalor wrote: > > On Tue, 31 Mar 2020 at 17:28, Amit Kapila wrote: > > > > On Mon, Mar 30, 2020 at 8:30 AM Mahendra Singh Thalor > > wrote: > > > > > > > > > 2077 if ((shared_balance >= VacuumCostLimit) && > > > > > > >>> CID ...: Incor

pgsql: Collect statistics about SLRU caches

2020-04-01 Thread Tomas Vondra
Collect statistics about SLRU caches There's a number of SLRU caches used to access important data like clog, commit timestamps, multixact, asynchronous notifications, etc. Until now we had no easy way to monitor these shared caches, compute hit ratios, number of reads/writes etc. This commit ext

pgsql: Clean up parsing of ltree and lquery some more.

2020-04-01 Thread Tom Lane
Clean up parsing of ltree and lquery some more. Fix lquery parsing to handle repeated flag characters correctly, and to enforce the max label length correctly in some cases where it did not before, and to detect empty labels in some cases where it did not before. In a more cosmetic vein, use a sw

pgsql: Add support for binary I/O of ltree, lquery, and ltxtquery types

2020-04-01 Thread Tom Lane
Add support for binary I/O of ltree, lquery, and ltxtquery types. Not much to say here --- does what it says on the tin. The "binary" representation in each case is really just the same as the text format, though we prefix a version-number byte in case anyone ever feels motivated to change that.

pgsql: Check equality semantics for unique indexes on partitioned table

2020-04-01 Thread Tom Lane
Check equality semantics for unique indexes on partitioned tables. We require the partition key to be a subset of the set of columns being made unique, so that physically-separate indexes on the different partitions are sufficient to enforce the uniqueness constraint. The existing code checked th

pgsql: Check equality semantics for unique indexes on partitioned table

2020-04-01 Thread Tom Lane
Check equality semantics for unique indexes on partitioned tables. We require the partition key to be a subset of the set of columns being made unique, so that physically-separate indexes on the different partitions are sufficient to enforce the uniqueness constraint. The existing code checked th

pgsql: Check equality semantics for unique indexes on partitioned table

2020-04-01 Thread Tom Lane
Check equality semantics for unique indexes on partitioned tables. We require the partition key to be a subset of the set of columns being made unique, so that physically-separate indexes on the different partitions are sufficient to enforce the uniqueness constraint. The existing code checked th

pgsql: Improve selectivity estimation for assorted match-style operator

2020-04-01 Thread Tom Lane
Improve selectivity estimation for assorted match-style operators. Quite a few matching operators such as JSONB's @> used "contsel" and "contjoinsel" as their selectivity estimators. That was a bad idea, because (a) contsel is only a stub, yielding a fixed default estimate, and (b) that default i

pgsql: Refactor code to look up local replication tuple

2020-04-01 Thread Peter Eisentraut
Refactor code to look up local replication tuple This unifies some duplicate code. Author: Amit Langote Discussion: https://www.postgresql.org/message-id/ca+hiwqfjye5anarxvkjr37aqmd52l-lztz9ld2qrlq3yfcy...@mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commi

pgsql: Update SQL features count

2020-04-01 Thread Peter Eisentraut
Update SQL features count The previously listed total of 179 does not appear to be correct for SQL:2016 anymore. (Previous SQL versions had slightly different feature sets, so it's plausible that it was once correct.) The currently correct count is the number of rows in the respective tables in

pgsql: Fix typo in contrib/intarray documentation

2020-04-01 Thread Alexander Korotkov
Fix typo in contrib/intarray documentation Reported-by: Erik Rijkers Discussion: https://postgr.es/m/82529ecf9bcc58d5b5cf9f3ffb699881%40xs4all.nl Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/4d276ba94fd9b19457aeb5b6d9af00589fe184a0 Modified Files --

pgsql: Correct CREATE INDEX documentation for opclass parameters

2020-04-01 Thread Alexander Korotkov
Correct CREATE INDEX documentation for opclass parameters Old versions of opclass parameters patch supported ability to specify DEFAULT as the opclass name in CREATE INDEX command. This ability was removed in the final version, but 911e702077 still mentions that in the documentation. Branch

pgsql: Documentation corrections for opclass parameters

2020-04-01 Thread Alexander Korotkov
Documentation corrections for opclass parameters Discussion: https://postgr.es/m/20200331024419.GB14618%40telsasoft.com Author: Justin Pryzby Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/3f1802e1fdb74a33db176291be27a2ec243511c6 Modified Files -- doc/