Re: .ready and .done files considered harmful
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Michael Paquier <michael@paquier.xyz>, Robert Haas <robertmhaas@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2024-12-12T15:53:00Z
Lists: pgsql-hackers
On Thu, Dec 12, 2024 at 04:29:47PM +0100, Alvaro Herrera wrote: > On 2024-Nov-14, Michael Paquier wrote: > >> On Wed, Nov 13, 2024 at 02:52:31PM -0500, Robert Haas wrote: >> > On Wed, Nov 13, 2024 at 11:05 AM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: >> >> So, my question now is, would there be much opposition to backpatching >> >> beb4e9ba1652 + 1fb17b190341 to REL_14_STABLE? >> > >> > It seems like it's been long enough now that if the new logic had >> > major problems we probably would have found them by now; so I feel >> > like it's probably pretty safe. Perhaps it's questionable how many >> > people we'll help by back-patching this into one additional release, >> > but if you feel it's worth it I wouldn't be inclined to argue. >> >> +1 for v14 as this version is still around for two years. > > Thanks, I have pushed it now. I'm happy to see these changes are proving to be useful! FWIW commit 756e221 should further reduce archiving overhead, but that may make it more likely that the server will attempt to re-archive files after a crash, so I'm not sure I would advise back-patching it. -- nathan
Commits
-
Reduce overhead of renaming archive status files.
- 756e221db610 16.0 cited
-
Improve performance of pgarch_readyXlog() with many status files.
- beb4e9ba1652 15.0 landed
-
Prioritize history files when archiving
- b981df4cc09a 12.0 cited