|From:||Michael Paquier <michael(at)paquier(dot)xyz>|
|To:||Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>|
|Subject:||Re: Logging query parmeters in auto_explain|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Tue, Jun 07, 2022 at 12:18:52PM +0100, Dagfinn Ilmari Mannsåker wrote:
> Point, fixed in the attached v2. I've also added a test that truncation
> and disabling works.
The tests are structured so as all the queries are run first, then the
full set of logs is slurped and scanned. With things like tests for
truncation, it becomes easier to have a given test overlap with
another one in terms of pattern matching, so we could silently lose
coverage. Wouldn't it be better to reorganize things so we save the
current size of the log file (as of -s $node->logfile), run one query,
and then slurp the log file based on the position saved previously?
The GUC updates had better be localized in each sub-section of the
tests, as well.
|Next Message||Michael Paquier||2022-06-09 01:48:27||Re: amcheck is using a wrong macro to check compressed-ness|
|Previous Message||Jonathan S. Katz||2022-06-09 01:15:12||June 16, 2022 out-of-cycle release for PostgreSQL 14|