| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: remove more archiving overhead |
| Date: | 2022-02-22 19:52:29 |
| Message-ID: | 20220222195229.GA42988@nathanxps13 |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 22, 2022 at 09:37:11AM -0800, Nathan Bossart wrote:
> In my testing, I found that when I killed the server just before unlink()
> during WAL recyling, I ended up with links to the same file in pg_wal after
> restarting. My latest test produced links to the same file for the current
> WAL file and the next one. Maybe WAL recyling should use durable_rename()
> instead of durable_rename_excl().
Here is an updated patch.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-reduce-archiving-overhead.patch | text/x-diff | 2.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2022-02-22 20:10:30 | Re: bailing out in tap tests nearly always a bad idea |
| Previous Message | Imseih (AWS), Sami | 2022-02-22 19:20:55 | [BUG] Panic due to incorrect missingContrecPtr after promotion |