| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Remove log_checkpoints = true from .pl tests |
| Date: | 2022-08-12 05:34:32 |
| Message-ID: | 87409.1660282472@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> writes:
> With commit 64da07c41a8c0a680460cdafc79093736332b6cf making default
> value of log_checkpoints to on, do we need to remove explicit settings
> in perl tests to save some (5) LOC?
I'm not particularly eager to do that, because I think defaulting
log_checkpoints to "on" was a bad decision that will eventually get
reverted. Even if that doesn't happen, we have *far* better ways
to spend our time than removing five lines of code, or even
discussing whether to do so.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2022-08-12 06:01:25 | build remaining Flex files standalone |
| Previous Message | Bharath Rupireddy | 2022-08-12 04:30:53 | Remove log_checkpoints = true from .pl tests |