pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Remove SQL regression tests for GUCs related to NO_SHOW_ALL 2+ messages / 1 participants [nested] [flat]
* pgsql: Remove SQL regression tests for GUCs related to NO_SHOW_ALL @ 2023-02-08 07:57 Michael Paquier <michael@paquier.xyz> 0 siblings, 0 replies; 2+ messages in thread From: Michael Paquier @ 2023-02-08 07:57 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Remove SQL regression tests for GUCs related to NO_SHOW_ALL No GUCs that use NO_SHOW_ALL are reported in pg_show_all_settings(), hence trying to check combinations of flags related to it is pointless. These queries have been introduced by d10e41d, so backpatch down to 15 to keep all the branches consistent. Equivalent checks based on NO_SHOW_ALL could be added in check_GUC_init() when a GUC is initially loaded, but this can be done only on HEAD. Author: Nitin Jadhav Discussion: https://postgr.es/m/CAMm1aWaYe0muu3ABo7iSAgK+OWDS9yNe8GGRYnCyeEpScYKa+g@mail.gmail.com Backpatch-through: 15 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/b7e84c65d5b2d694a669ae1db8ab1d6c51ef8596 Modified Files -------------- src/test/regress/expected/guc.out | 28 ---------------------------- src/test/regress/sql/guc.sql | 13 ------------- 2 files changed, 41 deletions(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: Remove SQL regression tests for GUCs related to NO_SHOW_ALL @ 2023-02-08 07:57 Michael Paquier <michael@paquier.xyz> 0 siblings, 0 replies; 2+ messages in thread From: Michael Paquier @ 2023-02-08 07:57 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Remove SQL regression tests for GUCs related to NO_SHOW_ALL No GUCs that use NO_SHOW_ALL are reported in pg_show_all_settings(), hence trying to check combinations of flags related to it is pointless. These queries have been introduced by d10e41d, so backpatch down to 15 to keep all the branches consistent. Equivalent checks based on NO_SHOW_ALL could be added in check_GUC_init() when a GUC is initially loaded, but this can be done only on HEAD. Author: Nitin Jadhav Discussion: https://postgr.es/m/CAMm1aWaYe0muu3ABo7iSAgK+OWDS9yNe8GGRYnCyeEpScYKa+g@mail.gmail.com Backpatch-through: 15 Branch ------ REL_15_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/dbe8a1726cfd5a09cf1ef99e76f5f89e2efada71 Modified Files -------------- src/test/regress/expected/guc.out | 28 ---------------------------- src/test/regress/sql/guc.sql | 13 ------------- 2 files changed, 41 deletions(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2023-02-08 07:57 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2023-02-08 07:57 pgsql: Remove SQL regression tests for GUCs related to NO_SHOW_ALL Michael Paquier <michael@paquier.xyz> 2023-02-08 07:57 pgsql: Remove SQL regression tests for GUCs related to NO_SHOW_ALL Michael Paquier <michael@paquier.xyz>
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