pgsql: Assign constraint name when cloning FK definition for partitions

2018-10-05 Thread Michael Paquier
Assign constraint name when cloning FK definition for partitions This is for example used when attaching a partition to a partitioned table which includes foreign keys, and in this case the constraint name has been missing in the data cloned. This could lead to hard crashes, as when validating th

pgsql: Assign constraint name when cloning FK definition for partitions

2018-10-05 Thread Michael Paquier
Assign constraint name when cloning FK definition for partitions This is for example used when attaching a partition to a partitioned table which includes foreign keys, and in this case the constraint name has been missing in the data cloned. This could lead to hard crashes, as when validating th

pgsql: doc: update PG 11 release notes

2018-10-05 Thread Bruce Momjian
doc: update PG 11 release notes Discussion: https://postgr.es/m/1f5b2e66-7ba8-98ec-c06a-aee9ff33f...@postgresql.org Author: Jonathan S. Katz Backpatch-through: 11 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/6eb612fea9d080f2ae77ecb7091e73dc9f298c97 Modified

pgsql: doc: update PG 11 release notes

2018-10-05 Thread Bruce Momjian
doc: update PG 11 release notes Discussion: https://postgr.es/m/1f5b2e66-7ba8-98ec-c06a-aee9ff33f...@postgresql.org Author: Jonathan S. Katz Backpatch-through: 11 Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/076cfffb39af281f4e3b7d9852715bb09e214171 Mo

pgsql: Allow btree comparison functions to return INT_MIN.

2018-10-05 Thread Tom Lane
Allow btree comparison functions to return INT_MIN. Historically we forbade datatype-specific comparison functions from returning INT_MIN, so that it would be safe to invert the sort order just by negating the comparison result. However, this was never really safe for comparison functions that di

pgsql: Allow btree comparison functions to return INT_MIN.

2018-10-05 Thread Tom Lane
Allow btree comparison functions to return INT_MIN. Historically we forbade datatype-specific comparison functions from returning INT_MIN, so that it would be safe to invert the sort order just by negating the comparison result. However, this was never really safe for comparison functions that di

pgsql: Allow btree comparison functions to return INT_MIN.

2018-10-05 Thread Tom Lane
Allow btree comparison functions to return INT_MIN. Historically we forbade datatype-specific comparison functions from returning INT_MIN, so that it would be safe to invert the sort order just by negating the comparison result. However, this was never really safe for comparison functions that di

pgsql: Allow btree comparison functions to return INT_MIN.

2018-10-05 Thread Tom Lane
Allow btree comparison functions to return INT_MIN. Historically we forbade datatype-specific comparison functions from returning INT_MIN, so that it would be safe to invert the sort order just by negating the comparison result. However, this was never really safe for comparison functions that di

pgsql: Allow btree comparison functions to return INT_MIN.

2018-10-05 Thread Tom Lane
Allow btree comparison functions to return INT_MIN. Historically we forbade datatype-specific comparison functions from returning INT_MIN, so that it would be safe to invert the sort order just by negating the comparison result. However, this was never really safe for comparison functions that di

pgsql: Allow btree comparison functions to return INT_MIN.

2018-10-05 Thread Tom Lane
Allow btree comparison functions to return INT_MIN. Historically we forbade datatype-specific comparison functions from returning INT_MIN, so that it would be safe to invert the sort order just by negating the comparison result. However, this was never really safe for comparison functions that di

pgsql: Allow btree comparison functions to return INT_MIN.

2018-10-05 Thread Tom Lane
Allow btree comparison functions to return INT_MIN. Historically we forbade datatype-specific comparison functions from returning INT_MIN, so that it would be safe to invert the sort order just by negating the comparison result. However, this was never really safe for comparison functions that di

Re: pgsql: Make WAL segment size configurable at initdb time.

2018-10-05 Thread David Steele
Hi Andres, On 10/5/18 5:54 PM, Andres Freund wrote: On 2018-09-20 11:48:08 -0400, David Steele wrote: diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index e1073ac6d3..3bfd172441 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -8440,10 +8440,8 @@ dynami

Re: pgsql: Make WAL segment size configurable at initdb time.

2018-10-05 Thread Andres Freund
On 2018-09-20 11:48:08 -0400, David Steele wrote: > Hi Andres, > > On 9/20/17 1:04 AM, Andres Freund wrote: > > > > Make WAL segment size configurable at initdb time. > > <...> > > > https://git.postgresql.org/pg/commitdiff/fc49e24fa69a15efacd5b8958115ed9c43c48f9a > It appears that fc49e24f miss

pgsql: Ensure that PLPGSQL_DTYPE_ROW variables have valid refname field

2018-10-05 Thread Tom Lane
Ensure that PLPGSQL_DTYPE_ROW variables have valid refname fields. Without this, the syntax-tree-dumping functions in pl_funcs.c crash, and there are other places that might be at risk too. Per report from Pavel Stehule. Looks like I broke this in commit f9263006d, so back-patch to v11. Discuss

pgsql: Ensure that PLPGSQL_DTYPE_ROW variables have valid refname field

2018-10-05 Thread Tom Lane
Ensure that PLPGSQL_DTYPE_ROW variables have valid refname fields. Without this, the syntax-tree-dumping functions in pl_funcs.c crash, and there are other places that might be at risk too. Per report from Pavel Stehule. Looks like I broke this in commit f9263006d, so back-patch to v11. Discuss

Re: pgsql: Make WAL segment size configurable at initdb time.

2018-10-05 Thread David Steele
On 9/21/18 12:44 PM, David Steele wrote: On 9/21/18 12:53 AM, Michael Paquier wrote: On Thu, Sep 20, 2018 at 06:23:54PM -0700, Andres Freund wrote: 16*M*B, right? If so, that's normal - pg_settings just reports the values in the underlying unit - which is XLOG_BLCKSZ, compile-time defaulting t

pgsql: Remove redundant allocation

2018-10-05 Thread Peter Eisentraut
Remove redundant allocation Author: Nikita Glukhov Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/b5f03dc7657e4cc62b975f3bc07b217916324a54 Modified Files -- contrib/jsonb_plpython/jsonb_plpython.c | 1 - 1 file changed, 1 deletion(-)

pgsql: Remove redundant allocation

2018-10-05 Thread Peter Eisentraut
Remove redundant allocation Author: Nikita Glukhov Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/40159d91cc546b2585efd3eb0b3db05cd6f2be93 Modified Files -- contrib/jsonb_plpython/jsonb_plpython.c | 1 - 1 file changed, 1 deletion(-)