pgsql: Fix pg_dump for disabled triggers on partitioned tables

2021-07-16 Thread Alvaro Herrera
Fix pg_dump for disabled triggers on partitioned tables pg_dump failed to preserve the 'enabled' flag (which can be not only disabled, but also REPLICA or ALWAYS) for partitions which had it changed from their respective parents. Attempt to handle that by including a definition for such triggers

pgsql: Fix pg_dump for disabled triggers on partitioned tables

2021-07-16 Thread Alvaro Herrera
Fix pg_dump for disabled triggers on partitioned tables pg_dump failed to preserve the 'enabled' flag (which can be not only disabled, but also REPLICA or ALWAYS) for partitions which had it changed from their respective parents. Attempt to handle that by including a definition for such triggers

pgsql: Fix pg_dump for disabled triggers on partitioned tables

2021-07-16 Thread Alvaro Herrera
Fix pg_dump for disabled triggers on partitioned tables pg_dump failed to preserve the 'enabled' flag (which can be not only disabled, but also REPLICA or ALWAYS) for partitions which had it changed from their respective parents. Attempt to handle that by including a definition for such triggers

pgsql: Fix pg_dump for disabled triggers on partitioned tables

2021-07-16 Thread Alvaro Herrera
Fix pg_dump for disabled triggers on partitioned tables pg_dump failed to preserve the 'enabled' flag (which can be not only disabled, but also REPLICA or ALWAYS) for partitions which had it changed from their respective parents. Attempt to handle that by including a definition for such triggers

pgsql: Fix pg_dump for disabled triggers on partitioned tables

2021-07-16 Thread Alvaro Herrera
Fix pg_dump for disabled triggers on partitioned tables pg_dump failed to preserve the 'enabled' flag (which can be not only disabled, but also REPLICA or ALWAYS) for partitions which had it changed from their respective parents. Attempt to handle that by including a definition for such triggers

pgsql: Preserve firing-on state when cloning row triggers to partitions

2021-07-16 Thread Alvaro Herrera
Preserve firing-on state when cloning row triggers to partitions When triggers are cloned from partitioned tables to their partitions, the 'tgenabled' flag (origin/replica/always/disable) was not propagated. Make it so that the flag on the trigger on partition is initially set to the same value as

pgsql: Preserve firing-on state when cloning row triggers to partitions

2021-07-16 Thread Alvaro Herrera
Preserve firing-on state when cloning row triggers to partitions When triggers are cloned from partitioned tables to their partitions, the 'tgenabled' flag (origin/replica/always/disable) was not propagated. Make it so that the flag on the trigger on partition is initially set to the same value as

pgsql: Preserve firing-on state when cloning row triggers to partitions

2021-07-16 Thread Alvaro Herrera
Preserve firing-on state when cloning row triggers to partitions When triggers are cloned from partitioned tables to their partitions, the 'tgenabled' flag (origin/replica/always/disable) was not propagated. Make it so that the flag on the trigger on partition is initially set to the same value as

pgsql: Preserve firing-on state when cloning row triggers to partitions

2021-07-16 Thread Alvaro Herrera
Preserve firing-on state when cloning row triggers to partitions When triggers are cloned from partitioned tables to their partitions, the 'tgenabled' flag (origin/replica/always/disable) was not propagated. Make it so that the flag on the trigger on partition is initially set to the same value as

pgsql: Preserve firing-on state when cloning row triggers to partitions

2021-07-16 Thread Alvaro Herrera
Preserve firing-on state when cloning row triggers to partitions When triggers are cloned from partitioned tables to their partitions, the 'tgenabled' flag (origin/replica/always/disable) was not propagated. Make it so that the flag on the trigger on partition is initially set to the same value as

pgsql: Advance old-segment horizon properly after slot invalidation

2021-07-16 Thread Alvaro Herrera
Advance old-segment horizon properly after slot invalidation When some slots are invalidated due to the max_slot_wal_keep_size limit, the old segment horizon should move forward to stay within the limit. However, in commit c6550776394e we forgot to call KeepLogSeg again to recompute the horizon af

pgsql: Advance old-segment horizon properly after slot invalidation

2021-07-16 Thread Alvaro Herrera
Advance old-segment horizon properly after slot invalidation When some slots are invalidated due to the max_slot_wal_keep_size limit, the old segment horizon should move forward to stay within the limit. However, in commit c6550776394e we forgot to call KeepLogSeg again to recompute the horizon af

pgsql: Advance old-segment horizon properly after slot invalidation

2021-07-16 Thread Alvaro Herrera
Advance old-segment horizon properly after slot invalidation When some slots are invalidated due to the max_slot_wal_keep_size limit, the old segment horizon should move forward to stay within the limit. However, in commit c6550776394e we forgot to call KeepLogSeg again to recompute the horizon af

pgsql: doc: Spell checking

2021-07-16 Thread Peter Eisentraut
doc: Spell checking Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/46111fb7b57876a87eb0630ec12ad30950e38a39 Modified Files -- doc/src/sgml/bki.sgml | 2 +- doc/src/sgml/fdwhandler.sgml | 2 +- doc/src/sgml/func.sgml | 4 +

pgsql: doc: Spell checking

2021-07-16 Thread Peter Eisentraut
doc: Spell checking Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/525115a332af0fd479503550fd4f82551b797aea Modified Files -- doc/src/sgml/bki.sgml | 2 +- doc/src/sgml/fdwhandler.sgml | 2 +- doc/src/sgml/func.sgml