| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_resetwal: Corrections around -c option |
| Date: | 2023-10-10 10:53:58 |
| Message-ID: | 202310101053.6jrlqjloog4q@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-Oct-10, Peter Eisentraut wrote:
> On 09.10.23 17:48, Alvaro Herrera wrote:
> > Hmm, not sure about this. [...]
>
> Would those issues also apply to the other SLRU-based guides on this man
> page? Are they all a bit wrong?
I didn't verify, but I think it's likely that they do and they are.
> > Not sure how to write this concisely, though. Should we really try?
>
> Maybe not. But the documentation currently suggests you can try (probably
> somewhat copy-and-pasted).
I bet this has not been thoroughly verified.
Perhaps we should have (somewhere outside the option list) a separate
paragraph that explains how to determine the safest maximum value to
use, and list only the multiplier together with each option.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias van de Meent | 2023-10-10 10:55:15 | Re: Comparing two double values method |
| Previous Message | Richard Guo | 2023-10-10 10:52:33 | Re: Check each of base restriction clauses for constant-FALSE-or-NULL |