Re: avoid multiple hard links to same WAL file after a crash

Поиск
Список
Период
Сортировка
Искать
От
Nathan Bossart
Тема
Re: avoid multiple hard links to same WAL file after a crash
Дата
Msg-id
20220426200935.GA3175655@nathanxps13
Ответ на
Список
Дерево обсуждения
avoid multiple hard links to same WAL file after a crash Nathan Bossart <nathandbossart@gmail.com>
Re: avoid multiple hard links to same WAL file after a crash Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: avoid multiple hard links to same WAL file after a crash Robert Haas <robertmhaas@gmail.com>
Re: avoid multiple hard links to same WAL file after a crash Tom Lane <tgl@sss.pgh.pa.us>
Re: avoid multiple hard links to same WAL file after a crash Nathan Bossart <nathandbossart@gmail.com>
Re: avoid multiple hard links to same WAL file after a crash Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: avoid multiple hard links to same WAL file after a crash Nathan Bossart <nathandbossart@gmail.com>
Re: avoid multiple hard links to same WAL file after a crash Michael Paquier <michael@paquier.xyz>
Re: avoid multiple hard links to same WAL file after a crash Nathan Bossart <nathandbossart@gmail.com>
Re: avoid multiple hard links to same WAL file after a crash Michael Paquier <michael@paquier.xyz>
Re: avoid multiple hard links to same WAL file after a crash Nathan Bossart <nathandbossart@gmail.com>
Re: avoid multiple hard links to same WAL file after a crash Nathan Bossart <nathandbossart@gmail.com>
Re: avoid multiple hard links to same WAL file after a crash Michael Paquier <michael@paquier.xyz>
Re: avoid multiple hard links to same WAL file after a crash Michael Paquier <michael@paquier.xyz>
Re: avoid multiple hard links to same WAL file after a crash Nathan Bossart <nathandbossart@gmail.com>
Re: avoid multiple hard links to same WAL file after a crash Michael Paquier <michael@paquier.xyz>
Back-patch of: avoid multiple hard links to same WAL file after a crash Robert Pang <robertpang@google.com>
Re: Back-patch of: avoid multiple hard links to same WAL file after a crash Nathan Bossart <nathandbossart@gmail.com>
Re: Back-patch of: avoid multiple hard links to same WAL file after a crash Andres Freund <andres@anarazel.de>
Re: avoid multiple hard links to same WAL file after a crash Robert Haas <robertmhaas@gmail.com>
Re: avoid multiple hard links to same WAL file after a crash Nathan Bossart <nathandbossart@gmail.com>
Re: avoid multiple hard links to same WAL file after a crash Nathan Bossart <nathandbossart@gmail.com>
Re: avoid multiple hard links to same WAL file after a crash Robert Haas <robertmhaas@gmail.com>
Re: avoid multiple hard links to same WAL file after a crash Justin Pryzby <pryzby@telsasoft.com>
Re: avoid multiple hard links to same WAL file after a crash Michael Paquier <michael@paquier.xyz>
Re: avoid multiple hard links to same WAL file after a crash Nathan Bossart <nathandbossart@gmail.com>
Re: avoid multiple hard links to same WAL file after a crash Tom Lane <tgl@sss.pgh.pa.us>
Re: avoid multiple hard links to same WAL file after a crash Greg Stark <stark@mit.edu>
Re: avoid multiple hard links to same WAL file after a crash Nathan Bossart <nathandbossart@gmail.com>
Re: avoid multiple hard links to same WAL file after a crash Michael Paquier <michael@paquier.xyz>
Re: avoid multiple hard links to same WAL file after a crash Nathan Bossart <nathandbossart@gmail.com>
Re: avoid multiple hard links to same WAL file after a crash Michael Paquier <michael@paquier.xyz>
Re: avoid multiple hard links to same WAL file after a crash Nathan Bossart <nathandbossart@gmail.com>
Here is an attempt at creating something that can be back-patched.  0001
simply replaces calls to durable_rename_excl() with durable_rename() and is
intended to be back-patched.  0002 removes the definition of
durable_rename_excl() and is _not_ intended for back-patching.  I imagine
0002 will need to be held back for v16devel.

I think back-patching 0001 will encounter a couple of small obstacles.  For
example, the call in basic_archive won't exist on most of the
back-branches, and durable_rename_excl() was named durable_link_or_rename()
before v13.  I don't mind producing a patch for each back-branch if needed.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
В списке pgsql-hackers по дате отправления
От: Tom Lane
Дата:
От: Robert Haas
Дата:
FAQ