From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_resetwal tests, logging, and docs update |
Date: | 2023-09-19 14:31:35 |
Message-ID: | b57e8115-709b-48f0-640c-2b82cf7b1473@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 13.09.23 16:36, Aleksander Alekseev wrote:
> All in all the patch looks OK but I have a couple of nitpicks.
>
> ```
> + working on a data directory in an unclean shutdown state or with a corrupt
> + control file.
> ```
>
> ```
> + After running this command on a data directory with corrupted WAL or a
> + corrupt control file,
> ```
>
> I'm not a native English speaker but shouldn't it be "corruptED control file"?
fixed
>
> ```
> + Force <command>pg_resetwal</command> to proceed even in situations where
> + it could be dangerous,
> ```
>
> "where" is probably fine but wouldn't "WHEN it could be dangerous" be better?
Hmm, I think I like "where" better.
Attached is an updated patch set where I have split the changes into
smaller pieces. The last two patches still have some open questions
about what certain constants mean etc. The other patches should be settled.
Attachment | Content-Type | Size |
---|---|---|
v2-0001-pg_resetwal-Update-an-obsolete-comment.patch | text/plain | 1020 bytes |
v2-0002-pg_resetwal-Improve-error-with-wrong-missing-data.patch | text/plain | 1.2 KB |
v2-0003-pg_resetwal-Regroup-help-output.patch | text/plain | 2.8 KB |
v2-0004-pg_resetwal-Use-frontend-logging-API.patch | text/plain | 2.0 KB |
v2-0005-doc-Improve-documentation-about-pg_resetwal-f-opt.patch | text/plain | 5.4 KB |
v2-0006-doc-pg_resetwal-Add-comments-how-the-multipliers-.patch | text/plain | 3.0 KB |
v2-0007-pg_resetwal-Add-more-tests-and-test-coverage.patch | text/plain | 7.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Cleveland | 2023-09-19 14:32:04 | Projection pushdown to index access method |
Previous Message | Steve Chavez | 2023-09-19 14:20:24 | Re: Add pg_basetype() function to obtain a DOMAIN base type |