pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Throw ERROR when publish_generated_columns is specified without 2+ messages / 1 participants [nested] [flat]
* pgsql: Throw ERROR when publish_generated_columns is specified without @ 2025-08-05 09:46 Amit Kapila <akapila@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: Amit Kapila @ 2025-08-05 09:46 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Throw ERROR when publish_generated_columns is specified without a value. Previously, specifying the publication option 'publish_generated_columns' without an explicit value would incorrectly default to 'stored', which is not the intended behavior. This patch fixes the issue by raising an ERROR when no value is provided for 'publish_generated_columns', ensuring that users must explicitly specify a valid option. Author: Peter Smith <smithpb2250@gmail.com> Reviewed-by: vignesh C <vignesh21@gmail.com> Backpatch-through: 18, where it was introduced Discussion: https://postgr.es/m/CAHut+PsCUCWiEKmB10DxhoPfXbF6jw5RD9ib2LuaQeA_XraW7w@mail.gmail.com Branch ------ REL_18_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/e5d04aedaf3a0e62dc22c42206bd258db24adddc Modified Files -------------- src/backend/commands/publicationcmds.c | 20 ++++++++++---------- src/test/regress/expected/publication.out | 15 ++++----------- src/test/regress/sql/publication.sql | 7 ++----- 3 files changed, 16 insertions(+), 26 deletions(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: Throw ERROR when publish_generated_columns is specified without @ 2025-08-05 09:46 Amit Kapila <akapila@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: Amit Kapila @ 2025-08-05 09:46 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Throw ERROR when publish_generated_columns is specified without a value. Previously, specifying the publication option 'publish_generated_columns' without an explicit value would incorrectly default to 'stored', which is not the intended behavior. This patch fixes the issue by raising an ERROR when no value is provided for 'publish_generated_columns', ensuring that users must explicitly specify a valid option. Author: Peter Smith <smithpb2250@gmail.com> Reviewed-by: vignesh C <vignesh21@gmail.com> Backpatch-through: 18, where it was introduced Discussion: https://postgr.es/m/CAHut+PsCUCWiEKmB10DxhoPfXbF6jw5RD9ib2LuaQeA_XraW7w@mail.gmail.com Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/c9a5860f7a56cc639d6a73519b8b2a00d26d960c Modified Files -------------- src/backend/commands/publicationcmds.c | 20 ++++++++++---------- src/test/regress/expected/publication.out | 15 ++++----------- src/test/regress/sql/publication.sql | 7 ++----- 3 files changed, 16 insertions(+), 26 deletions(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2025-08-05 09:46 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-08-05 09:46 pgsql: Throw ERROR when publish_generated_columns is specified without Amit Kapila <akapila@postgresql.org> 2025-08-05 09:46 pgsql: Throw ERROR when publish_generated_columns is specified without Amit Kapila <akapila@postgresql.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox