[COMMITTERS] pgsql: Fire per-statement triggers on partitioned tables.
Fire per-statement triggers on partitioned tables. Even though no actual tuples are ever inserted into a partitioned table (the actual tuples are in the partitions, not the partitioned table itself), we still need to have a ResultRelInfo for the partitioned table, or per-statement triggers won't get fired. Amit Langote, per a report from Rajkumar Raghuwanshi. Reviewed by me. Discussion: http://postgr.es/m/CAKcux6%3DwYospCRY2J4XEFuVy0L41S%3Dfic7rmkbsU-GXhhSbmBg%40mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/e180c8aa8caf5c55a273d4a8e6092e77ff3cff10 Modified Files -- doc/src/sgml/trigger.sgml | 19 src/backend/executor/execMain.c | 55 -- src/backend/executor/nodeModifyTable.c | 42 + src/backend/nodes/copyfuncs.c | 2 + src/backend/nodes/outfuncs.c| 3 ++ src/backend/nodes/readfuncs.c | 2 + src/backend/optimizer/plan/createplan.c | 1 + src/backend/optimizer/plan/planner.c| 3 ++ src/backend/optimizer/plan/setrefs.c| 19 ++-- src/include/nodes/execnodes.h | 12 + src/include/nodes/plannodes.h | 13 +- src/include/nodes/relation.h| 1 + src/test/regress/expected/triggers.out | 81 + src/test/regress/sql/triggers.sql | 70 14 files changed, 296 insertions(+), 27 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix logical replication launcher wake up and reset
Fix logical replication launcher wake up and reset After the logical replication launcher was told to wake up at commit (for example, by a CREATE SUBSCRIPTION command), the flag to wake up was not reset, so it would be woken up at every following commit as well. So fix that by resetting the flag. Also, we don't need to wake up anything if the transaction was rolled back. Just reset the flag in that case. Author: Masahiko Sawada Reported-by: Fujii Masao Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/9414e41ea703ea5fcc288bcf7dc000e53306896b Modified Files -- src/backend/access/transam/xact.c | 3 ++- src/backend/replication/logical/launcher.c | 6 -- src/include/replication/logicallauncher.h | 2 +- 3 files changed, 7 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Allow vcregress.pl to run an arbitrary TAP test set
Allow vcregress.pl to run an arbitrary TAP test set Currently only provision for running the bin checks in a single step is provided for. Now these tests can be run individually, as well as tests in other locations (e.g. src.test/recover). Also provide for suppressing unnecessary temp installs by setting the NO_TEMP_INSTALL environment variable just as the Makefiles do. Backpatch to 9.4. Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/66510630d8621a638b487fa5ae685bdc60240440 Modified Files -- src/tools/msvc/vcregress.pl | 48 - 1 file changed, 30 insertions(+), 18 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Allow vcregress.pl to run an arbitrary TAP test set
Allow vcregress.pl to run an arbitrary TAP test set Currently only provision for running the bin checks in a single step is provided for. Now these tests can be run individually, as well as tests in other locations (e.g. src.test/recover). Also provide for suppressing unnecessary temp installs by setting the NO_TEMP_INSTALL environment variable just as the Makefiles do. Backpatch to 9.4. Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/263e33d979fc19d889f914977978f9326cc8a3e4 Modified Files -- src/tools/msvc/vcregress.pl | 58 - 1 file changed, 41 insertions(+), 17 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Allow vcregress.pl to run an arbitrary TAP test set
Allow vcregress.pl to run an arbitrary TAP test set Currently only provision for running the bin checks in a single step is provided for. Now these tests can be run individually, as well as tests in other locations (e.g. src.test/recover). Also provide for suppressing unnecessary temp installs by setting the NO_TEMP_INSTALL environment variable just as the Makefiles do. Backpatch to 9.4. Branch -- REL9_4_STABLE Details --- https://git.postgresql.org/pg/commitdiff/3c1e14af8692d48548adac9b8a0cbabaa8a92b78 Modified Files -- src/tools/msvc/vcregress.pl | 58 - 1 file changed, 41 insertions(+), 17 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Allow vcregress.pl to run an arbitrary TAP test set
Allow vcregress.pl to run an arbitrary TAP test set Currently only provision for running the bin checks in a single step is provided for. Now these tests can be run individually, as well as tests in other locations (e.g. src.test/recover). Also provide for suppressing unnecessary temp installs by setting the NO_TEMP_INSTALL environment variable just as the Makefiles do. Backpatch to 9.4. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/fed6df486dca1b9e53d3f560031b9a236c99f4bb Modified Files -- src/tools/msvc/vcregress.pl | 50 - 1 file changed, 31 insertions(+), 19 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: libpq: Fix inadvertent change in .pgpass lookup behavior.
libpq: Fix inadvertent change in .pgpass lookup behavior. Commit 274bb2b3857cc987cfa21d14775cae9b0dababa5 caused password file lookups to use the hostaddr in preference to the host, but that was not intended and the documented behavior is the opposite. Report and patch by Kyotaro Horiguchi. Discussion: http://postgr.es/m/20170428.165432.60857995.horiguchi.kyot...@lab.ntt.co.jp Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/bdac9836d3b910c5fd592aaeaac3c2e2e1defcad Modified Files -- src/interfaces/libpq/fe-connect.c | 13 +++-- 1 file changed, 11 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update time zone data files to tzdata release 2017b.
Update time zone data files to tzdata release 2017b. DST law changes in Chile, Haiti, and Mongolia. Historical corrections for Ecuador, Kazakhstan, Liberia, and Spain. The IANA crew continue their campaign to replace invented time zone abbrevations with numeric GMT offsets. This update changes numerous zones in South America, the Pacific and Indian oceans, and some Asian and Middle Eastern zones. I kept these abbreviations in the tznames/ data files, however, so that we will still accept them for input. (We may want to start trimming those files someday, but I think we should wait for the upstream dust to settle before deciding what to do.) In passing, add MESZ (Mitteleuropaeische Sommerzeit) to the tznames lists; since we accept MEZ (Mitteleuropaeische Zeit) it seems rather strange not to take the other one. And fix some incorrect, or at least obsolete, comments that certain abbreviations are not traceable to the IANA data. Branch -- REL9_3_STABLE Details --- https://git.postgresql.org/pg/commitdiff/dc93cafcad89d3e626986166ef0fb87f53ead521 Modified Files -- src/timezone/data/africa| 126 src/timezone/data/antarctica| 3 +- src/timezone/data/asia | 312 ++-- src/timezone/data/australasia | 159 +-- src/timezone/data/backward | 1 + src/timezone/data/backzone | 138 + src/timezone/data/europe| 204 +++-- src/timezone/data/northamerica | 95 --- src/timezone/data/southamerica | 554 ++-- src/timezone/known_abbrevs.txt | 113 ++-- src/timezone/tznames/America.txt| 106 ++- src/timezone/tznames/Antarctica.txt | 11 +- src/timezone/tznames/Asia.txt | 86 ++ src/timezone/tznames/Atlantic.txt | 15 +- src/timezone/tznames/Australia.txt | 9 +- src/timezone/tznames/Default| 288 ++- src/timezone/tznames/Europe.txt | 11 +- src/timezone/tznames/Indian.txt | 24 +- src/timezone/tznames/Pacific.txt| 103 +++ src/timezone/tznames/README | 12 +- 20 files changed, 1063 insertions(+), 1307 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update time zone data files to tzdata release 2017b.
Update time zone data files to tzdata release 2017b. DST law changes in Chile, Haiti, and Mongolia. Historical corrections for Ecuador, Kazakhstan, Liberia, and Spain. The IANA crew continue their campaign to replace invented time zone abbrevations with numeric GMT offsets. This update changes numerous zones in South America, the Pacific and Indian oceans, and some Asian and Middle Eastern zones. I kept these abbreviations in the tznames/ data files, however, so that we will still accept them for input. (We may want to start trimming those files someday, but I think we should wait for the upstream dust to settle before deciding what to do.) In passing, add MESZ (Mitteleuropaeische Sommerzeit) to the tznames lists; since we accept MEZ (Mitteleuropaeische Zeit) it seems rather strange not to take the other one. And fix some incorrect, or at least obsolete, comments that certain abbreviations are not traceable to the IANA data. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/74a20d0ab7c99b3efcf5dc7aac741e3b2f952a34 Modified Files -- src/timezone/data/africa| 126 src/timezone/data/antarctica| 3 +- src/timezone/data/asia | 312 ++-- src/timezone/data/australasia | 159 +-- src/timezone/data/backward | 1 + src/timezone/data/backzone | 138 + src/timezone/data/europe| 204 +++-- src/timezone/data/northamerica | 95 --- src/timezone/data/southamerica | 554 ++-- src/timezone/known_abbrevs.txt | 113 ++-- src/timezone/tznames/America.txt| 106 ++- src/timezone/tznames/Antarctica.txt | 11 +- src/timezone/tznames/Asia.txt | 86 ++ src/timezone/tznames/Atlantic.txt | 15 +- src/timezone/tznames/Australia.txt | 9 +- src/timezone/tznames/Default| 288 ++- src/timezone/tznames/Europe.txt | 11 +- src/timezone/tznames/Indian.txt | 24 +- src/timezone/tznames/Pacific.txt| 103 +++ src/timezone/tznames/README | 12 +- 20 files changed, 1063 insertions(+), 1307 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update time zone data files to tzdata release 2017b.
Update time zone data files to tzdata release 2017b. DST law changes in Chile, Haiti, and Mongolia. Historical corrections for Ecuador, Kazakhstan, Liberia, and Spain. The IANA crew continue their campaign to replace invented time zone abbrevations with numeric GMT offsets. This update changes numerous zones in South America, the Pacific and Indian oceans, and some Asian and Middle Eastern zones. I kept these abbreviations in the tznames/ data files, however, so that we will still accept them for input. (We may want to start trimming those files someday, but I think we should wait for the upstream dust to settle before deciding what to do.) In passing, add MESZ (Mitteleuropaeische Sommerzeit) to the tznames lists; since we accept MEZ (Mitteleuropaeische Zeit) it seems rather strange not to take the other one. And fix some incorrect, or at least obsolete, comments that certain abbreviations are not traceable to the IANA data. Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/1fdc3f6e8afe580c30515c70a04d074d527ae780 Modified Files -- src/timezone/data/africa| 126 src/timezone/data/antarctica| 3 +- src/timezone/data/asia | 312 ++-- src/timezone/data/australasia | 159 +-- src/timezone/data/backward | 1 + src/timezone/data/backzone | 138 + src/timezone/data/europe| 204 +++-- src/timezone/data/northamerica | 95 --- src/timezone/data/southamerica | 554 ++-- src/timezone/known_abbrevs.txt | 113 ++-- src/timezone/tznames/America.txt| 106 ++- src/timezone/tznames/Antarctica.txt | 11 +- src/timezone/tznames/Asia.txt | 86 ++ src/timezone/tznames/Atlantic.txt | 15 +- src/timezone/tznames/Australia.txt | 9 +- src/timezone/tznames/Default| 288 ++- src/timezone/tznames/Europe.txt | 11 +- src/timezone/tznames/Indian.txt | 24 +- src/timezone/tznames/Pacific.txt| 103 +++ src/timezone/tznames/README | 12 +- 20 files changed, 1063 insertions(+), 1307 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update time zone data files to tzdata release 2017b.
Update time zone data files to tzdata release 2017b. DST law changes in Chile, Haiti, and Mongolia. Historical corrections for Ecuador, Kazakhstan, Liberia, and Spain. The IANA crew continue their campaign to replace invented time zone abbrevations with numeric GMT offsets. This update changes numerous zones in South America, the Pacific and Indian oceans, and some Asian and Middle Eastern zones. I kept these abbreviations in the tznames/ data files, however, so that we will still accept them for input. (We may want to start trimming those files someday, but I think we should wait for the upstream dust to settle before deciding what to do.) In passing, add MESZ (Mitteleuropaeische Sommerzeit) to the tznames lists; since we accept MEZ (Mitteleuropaeische Zeit) it seems rather strange not to take the other one. And fix some incorrect, or at least obsolete, comments that certain abbreviations are not traceable to the IANA data. Branch -- REL9_4_STABLE Details --- https://git.postgresql.org/pg/commitdiff/1c88623465d849c90fa529dc661b0b16730cbe91 Modified Files -- src/timezone/data/africa| 126 src/timezone/data/antarctica| 3 +- src/timezone/data/asia | 312 ++-- src/timezone/data/australasia | 159 +-- src/timezone/data/backward | 1 + src/timezone/data/backzone | 138 + src/timezone/data/europe| 204 +++-- src/timezone/data/northamerica | 95 --- src/timezone/data/southamerica | 554 ++-- src/timezone/known_abbrevs.txt | 113 ++-- src/timezone/tznames/America.txt| 106 ++- src/timezone/tznames/Antarctica.txt | 11 +- src/timezone/tznames/Asia.txt | 86 ++ src/timezone/tznames/Atlantic.txt | 15 +- src/timezone/tznames/Australia.txt | 9 +- src/timezone/tznames/Default| 288 ++- src/timezone/tznames/Europe.txt | 11 +- src/timezone/tznames/Indian.txt | 24 +- src/timezone/tznames/Pacific.txt| 103 +++ src/timezone/tznames/README | 12 +- 20 files changed, 1063 insertions(+), 1307 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update time zone data files to tzdata release 2017b.
Update time zone data files to tzdata release 2017b. DST law changes in Chile, Haiti, and Mongolia. Historical corrections for Ecuador, Kazakhstan, Liberia, and Spain. The IANA crew continue their campaign to replace invented time zone abbrevations with numeric GMT offsets. This update changes numerous zones in South America, the Pacific and Indian oceans, and some Asian and Middle Eastern zones. I kept these abbreviations in the tznames/ data files, however, so that we will still accept them for input. (We may want to start trimming those files someday, but I think we should wait for the upstream dust to settle before deciding what to do.) In passing, add MESZ (Mitteleuropaeische Sommerzeit) to the tznames lists; since we accept MEZ (Mitteleuropaeische Zeit) it seems rather strange not to take the other one. And fix some incorrect, or at least obsolete, comments that certain abbreviations are not traceable to the IANA data. Branch -- REL9_2_STABLE Details --- https://git.postgresql.org/pg/commitdiff/c96ccc40e41028baff770a1f537059dda4bd76b3 Modified Files -- src/timezone/data/africa| 126 src/timezone/data/antarctica| 3 +- src/timezone/data/asia | 312 ++-- src/timezone/data/australasia | 159 +-- src/timezone/data/backward | 1 + src/timezone/data/backzone | 138 + src/timezone/data/europe| 204 +++-- src/timezone/data/northamerica | 95 --- src/timezone/data/southamerica | 554 ++-- src/timezone/known_abbrevs.txt | 113 ++-- src/timezone/tznames/America.txt| 106 ++- src/timezone/tznames/Antarctica.txt | 11 +- src/timezone/tznames/Asia.txt | 86 ++ src/timezone/tznames/Atlantic.txt | 15 +- src/timezone/tznames/Australia.txt | 9 +- src/timezone/tznames/Default| 288 ++- src/timezone/tznames/Europe.txt | 11 +- src/timezone/tznames/Indian.txt | 24 +- src/timezone/tznames/Pacific.txt| 103 +++ src/timezone/tznames/README | 12 +- 20 files changed, 1063 insertions(+), 1307 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Update time zone data files to tzdata release 2017b.
Update time zone data files to tzdata release 2017b. DST law changes in Chile, Haiti, and Mongolia. Historical corrections for Ecuador, Kazakhstan, Liberia, and Spain. The IANA crew continue their campaign to replace invented time zone abbrevations with numeric GMT offsets. This update changes numerous zones in South America, the Pacific and Indian oceans, and some Asian and Middle Eastern zones. I kept these abbreviations in the tznames/ data files, however, so that we will still accept them for input. (We may want to start trimming those files someday, but I think we should wait for the upstream dust to settle before deciding what to do.) In passing, add MESZ (Mitteleuropaeische Sommerzeit) to the tznames lists; since we accept MEZ (Mitteleuropaeische Zeit) it seems rather strange not to take the other one. And fix some incorrect, or at least obsolete, comments that certain abbreviations are not traceable to the IANA data. Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/9a8cc157c6e4724770168c589844539ccff2bd05 Modified Files -- src/timezone/data/africa| 126 src/timezone/data/antarctica| 3 +- src/timezone/data/asia | 312 ++-- src/timezone/data/australasia | 159 +-- src/timezone/data/backward | 1 + src/timezone/data/backzone | 138 + src/timezone/data/europe| 204 +++-- src/timezone/data/northamerica | 95 --- src/timezone/data/southamerica | 554 ++-- src/timezone/known_abbrevs.txt | 113 ++-- src/timezone/tznames/America.txt| 106 ++- src/timezone/tznames/Antarctica.txt | 11 +- src/timezone/tznames/Asia.txt | 86 ++ src/timezone/tznames/Atlantic.txt | 15 +- src/timezone/tznames/Australia.txt | 9 +- src/timezone/tznames/Default| 288 ++- src/timezone/tznames/Europe.txt | 11 +- src/timezone/tznames/Indian.txt | 24 +- src/timezone/tznames/Pacific.txt| 103 +++ src/timezone/tznames/README | 12 +- 20 files changed, 1063 insertions(+), 1307 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix mis-optimization of semijoins with more than one LHS relatio
Fix mis-optimization of semijoins with more than one LHS relation. The inner-unique patch (commit 9c7f5229a) supposed that if we're considering a JOIN_UNIQUE_INNER join path, we can always set inner_unique for the join, because the inner path produced by create_unique_path should be unique relative to the outer relation. However, that's true only if we're considering joining to the whole outer relation --- otherwise we may be applying only some of the join quals, and so the inner path might be non-unique from the perspective of this join. Adjust the test to only believe that we can set inner_unique if we have the whole semijoin LHS on the outer side. There is more that can be done in this area, but this commit is only intended to provide the minimal fix needed to get correct plans. Per report from Teodor Sigaev. Thanks to David Rowley for preliminary investigation. Discussion: https://postgr.es/m/f994fc98-389f-4a46-d1bc-c42e05cb4...@sigaev.ru Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/2057a58d1629ebffce694e3cef7f714571a88dd7 Modified Files -- src/backend/optimizer/path/joinpath.c | 10 +++--- src/test/regress/expected/join.out| 29 + src/test/regress/sql/join.sql | 8 3 files changed, 44 insertions(+), 3 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Reduce semijoins with unique inner relations to plain inner join
Reduce semijoins with unique inner relations to plain inner joins. If the inner relation can be proven unique, that is it can have no more than one matching row for any row of the outer query, then we might as well implement the semijoin as a plain inner join, allowing substantially more freedom to the planner. This is a form of outer join strength reduction, but it can't be implemented in reduce_outer_joins() because we don't have enough info about the individual relations at that stage. Instead do it much like remove_useless_joins(): once we've built base relations, we can make another pass over the SpecialJoinInfo list and get rid of any entries representing reducible semijoins. This is essentially a followon to the inner-unique patch (commit 9c7f5229a) and makes use of the proof machinery that that patch created. We need only minor refactoring of innerrel_is_unique's API to support this usage. Per performance complaint from Teodor Sigaev. Discussion: https://postgr.es/m/f994fc98-389f-4a46-d1bc-c42e05cb4...@sigaev.ru Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/92a43e4857d9682b93c9f755f453cc8fd7c66c81 Modified Files -- src/backend/optimizer/path/joinpath.c | 32 --- src/backend/optimizer/plan/analyzejoins.c | 121 +++--- src/backend/optimizer/plan/planmain.c | 6 ++ src/include/optimizer/planmain.h | 5 +- src/test/regress/expected/join.out| 28 ++ src/test/regress/expected/updatable_views.out | 2 +- src/test/regress/sql/join.sql | 14 +++ 7 files changed, 181 insertions(+), 27 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Improve function header comment for create_singleton_array().
Improve function header comment for create_singleton_array(). Mentioning the caller is neither future-proof nor an adequate substitute for giving an API specification. Per gripe from Neha Khatri, though I changed the patch around some. Discussion: https://postgr.es/m/cafo0u+_fs5srhzq6upg+4fberhoa9n2+nprtvac9mmewivx...@mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/54affb41e79cf4bec00bb5e00eb12a1715b9e278 Modified Files -- src/backend/utils/adt/array_userfuncs.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Don't wake up logical replication launcher unnecessarily
Don't wake up logical replication launcher unnecessarily In CREATE SUBSCRIPTION, only wake up the launcher when the subscription is enabled. Author: Fujii Masao Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/a99448ab4515aaadc17647e53633f418893f5adf Modified Files -- src/backend/commands/subscriptioncmds.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
