Re: Change ereport level for QueuePartitionConstraintValidation
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: David Rowley <david.rowley@2ndquadrant.com>
Cc: Thomas Munro <thomas.munro@gmail.com>, Sergei Kornilov <sk@zsrv.org>, PostgreSQL mailing lists <pgsql-hackers@postgresql.org>, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Robert Haas <robertmhaas@gmail.com>
Date: 2019-07-17T17:56:27Z
Lists: pgsql-hackers
On 2019-Jul-15, David Rowley wrote: > I think the only argument against it was around lack of ability to > test if the constraint was used to verify no row breaks the partition > bound during the ATTACH PARTITION. Would it work to set client_min_messages to DEBUG1 for the duration of the test, or does that have too much unrelated noise? > Does anyone feel strongly that we need to the test to confirm that the > constraint was used for this? Well, IME if we don't test it, we're sure to break it in the future. The only questions are 1) when, 2) how long till we notice, 3) how difficult is it to fix at that point. I think breakage is easily noticed by users, and a fix is unlikely to require hard measures such as ABI breaks or catversion bumps. I'd like more than zero tests, but it doesn't seem *that* severe. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Avoid using INFO elevel for what are fundamentally debug messages.
- db438318997b 13.0 landed
- 121e3ceed6d9 12.0 landed
-
Revert setting client_min_messages to 'debug1' in new tests.
- 5655565c077c 12.0 cited