Re: .ready and .done files considered harmful
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Stephen Frost <sfrost@snowman.net>, Dilip Kumar <dilipbalaut@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2021-05-05T20:36:53Z
Lists: pgsql-hackers
On Wed, May 5, 2021 at 4:31 PM Andres Freund <andres@anarazel.de> wrote: > On 2021-05-05 16:22:21 -0400, Robert Haas wrote: > > Huh, I had not thought about that problem. So, at the risk of getting > > sidetracked, what exactly are you asking for here? Let the extension > > pick the timeline using an algorithm of its own devising, rather than > > having core do it? Or what? > > Not Stephen, but to me the most reasonable way to address this is to > make timeline identifier wider and randomly allocated. The sequential > looking natures of timelines imo is actively unhelpful. Yeah, I always wondered why we didn't assign them randomly. -- Robert Haas EDB: http://www.enterprisedb.com
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