[COMMITTERS] pgsql: pg_basebackup: Add option to create replication slot

2017-09-27 Thread Peter Eisentraut
pg_basebackup: Add option to create replication slot When requesting a particular replication slot, the new pg_basebackup option -C/--create-slot creates it before starting to replicate from it. Further refactor the slot creation logic to include the temporary slot creation logic into the same fu

[COMMITTERS] pgsql: Get rid of parameterized marked sections in SGML

2017-09-27 Thread Peter Eisentraut
Get rid of parameterized marked sections in SGML Previously, we created a variant of the installation instructions for producing the plain-text INSTALL file by marking up certain parts of installation.sgml using SGML parameterized marked sections. Marked sections will not work anymore in XML, so

[COMMITTERS] pgsql: Improve vpath support in plperl build

2017-09-27 Thread Peter Eisentraut
Improve vpath support in plperl build Run xsubpp with the -output option instead of redirecting stdout. That ensures that the #line directives in the output file point to the right place in a vpath build. This in turn fixes an error in coverage builds that it can't find the source files. Refact

[COMMITTERS] pgsql: Improve the CREATE POLICY documentation.

2017-09-27 Thread Dean Rasheed
Improve the CREATE POLICY documentation. Provide a correct description of how multiple policies are combined, clarify when SELECT permissions are required, mention SELECT FOR UPDATE/SHARE, and do some other more minor tidying up. Reviewed by Stephen Frost Discussion: https://postgr.es/m/CAEZATC

[COMMITTERS] pgsql: Improve the CREATE POLICY documentation.

2017-09-27 Thread Dean Rasheed
Improve the CREATE POLICY documentation. Provide a correct description of how multiple policies are combined, clarify when SELECT permissions are required, mention SELECT FOR UPDATE/SHARE, and do some other more minor tidying up. Reviewed by Stephen Frost Discussion: https://postgr.es/m/CAEZATC

[COMMITTERS] pgsql: Improve the CREATE POLICY documentation.

2017-09-27 Thread Dean Rasheed
Improve the CREATE POLICY documentation. Provide a correct description of how multiple policies are combined, clarify when SELECT permissions are required, mention SELECT FOR UPDATE/SHARE, and do some other more minor tidying up. Reviewed by Stephen Frost Discussion: https://postgr.es/m/CAEZATC

[COMMITTERS] pgsql: Improve the CREATE POLICY documentation.

2017-09-27 Thread Dean Rasheed
Improve the CREATE POLICY documentation. Provide a correct description of how multiple policies are combined, clarify when SELECT permissions are required, mention SELECT FOR UPDATE/SHARE, and do some other more minor tidying up. Reviewed by Stephen Frost Discussion: https://postgr.es/m/CAEZATC

Re: [COMMITTERS] pgsql: Improve vpath support in plperl build

2017-09-27 Thread Tom Lane
Peter Eisentraut writes: > Improve vpath support in plperl build A fair chunk of the buildfarm doesn't like this. It looks like xsubpp's "-output" option is a johnny-come-lately. regards, tom lane -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.

[COMMITTERS] pgsql: Fix plperl build

2017-09-27 Thread Peter Eisentraut
Fix plperl build The changes in 639928c988c1c2f52bbe7ca89e8c7c78a041b3e2 turned out to require Perl 5.9.3, which is newer than our minimum required version. So revert back to the old code for the normal case and only use the new variant when both coverage and vpath are used. As the minimum Perl v

Re: [COMMITTERS] pgsql: Improve vpath support in plperl build

2017-09-27 Thread Peter Eisentraut
On 9/27/17 15:14, Tom Lane wrote: > Peter Eisentraut writes: >> Improve vpath support in plperl build > > A fair chunk of the buildfarm doesn't like this. It looks like > xsubpp's "-output" option is a johnny-come-lately. Yup, fixed that. -- Peter Eisentraut http://www.2ndQuadran

[COMMITTERS] pgsql: Revert to 9.6 treatment of ALTER TYPE enumtype ADD VALUE.

2017-09-27 Thread Tom Lane
Revert to 9.6 treatment of ALTER TYPE enumtype ADD VALUE. This reverts commit 15bc038f9, along with the followon commits 1635e80d3 and 984c92074 that tried to clean up the problems exposed by bug #14825. The result was incomplete because it failed to address parallel-query requirements. With 10.0

[COMMITTERS] pgsql: Revert to 9.6 treatment of ALTER TYPE enumtype ADD VALUE.

2017-09-27 Thread Tom Lane
Revert to 9.6 treatment of ALTER TYPE enumtype ADD VALUE. This reverts commit 15bc038f9, along with the followon commits 1635e80d3 and 984c92074 that tried to clean up the problems exposed by bug #14825. The result was incomplete because it failed to address parallel-query requirements. With 10.0

[COMMITTERS] pgsql: Fix behavior when converting a float infinity to numeric.

2017-09-27 Thread Tom Lane
Fix behavior when converting a float infinity to numeric. float8_numeric() and float4_numeric() failed to consider the possibility that the input is an IEEE infinity. The results depended on the platform-specific behavior of sprintf(): on most platforms you'd get something like ERROR: invalid i

[COMMITTERS] pgsql: Fix behavior when converting a float infinity to numeric.

2017-09-27 Thread Tom Lane
Fix behavior when converting a float infinity to numeric. float8_numeric() and float4_numeric() failed to consider the possibility that the input is an IEEE infinity. The results depended on the platform-specific behavior of sprintf(): on most platforms you'd get something like ERROR: invalid i

[COMMITTERS] pgsql: Fix behavior when converting a float infinity to numeric.

2017-09-27 Thread Tom Lane
Fix behavior when converting a float infinity to numeric. float8_numeric() and float4_numeric() failed to consider the possibility that the input is an IEEE infinity. The results depended on the platform-specific behavior of sprintf(): on most platforms you'd get something like ERROR: invalid i

[COMMITTERS] pgsql: Fix behavior when converting a float infinity to numeric.

2017-09-27 Thread Tom Lane
Fix behavior when converting a float infinity to numeric. float8_numeric() and float4_numeric() failed to consider the possibility that the input is an IEEE infinity. The results depended on the platform-specific behavior of sprintf(): on most platforms you'd get something like ERROR: invalid i

[COMMITTERS] pgsql: Fix behavior when converting a float infinity to numeric.

2017-09-27 Thread Tom Lane
Fix behavior when converting a float infinity to numeric. float8_numeric() and float4_numeric() failed to consider the possibility that the input is an IEEE infinity. The results depended on the platform-specific behavior of sprintf(): on most platforms you'd get something like ERROR: invalid i

[COMMITTERS] pgsql: Fix behavior when converting a float infinity to numeric.

2017-09-27 Thread Tom Lane
Fix behavior when converting a float infinity to numeric. float8_numeric() and float4_numeric() failed to consider the possibility that the input is an IEEE infinity. The results depended on the platform-specific behavior of sprintf(): on most platforms you'd get something like ERROR: invalid i

[COMMITTERS] pgsql: Fix behavior when converting a float infinity to numeric.

2017-09-27 Thread Tom Lane
Fix behavior when converting a float infinity to numeric. float8_numeric() and float4_numeric() failed to consider the possibility that the input is an IEEE infinity. The results depended on the platform-specific behavior of sprintf(): on most platforms you'd get something like ERROR: invalid i

PartitionSchemaData & partcollation (Re: [COMMITTERS] pgsql: Associate partitioning information with each RelOptInfo.)

2017-09-27 Thread Amit Langote
On 2017/09/21 12:42, Robert Haas wrote: > Associate partitioning information with each RelOptInfo. > > This is not used for anything yet, but it is necessary infrastructure > for partition-wise join and for partition pruning without constraint > exclusion. > > Ashutosh Bapat, reviewed by Amit Lan

Re: [HACKERS] PartitionSchemaData & partcollation (Re: [COMMITTERS] pgsql: Associate partitioning information with each RelOptInfo.)

2017-09-27 Thread Amit Langote
Sorry, I meant to say PartitionSchem"e"Data in subject. Thanks, Amit -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers