Re: [Patch] pg_rewind: options to use restore_command from recovery.conf or command line
Alexander Korotkov <a.korotkov@postgrespro.ru>
From: Alexander Korotkov <a.korotkov@postgrespro.ru>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Michael Paquier <michael@paquier.xyz>,
Alexey Kondratov <a.kondratov@postgrespro.ru>, Alvaro Herrera <alvherre@2ndquadrant.com>,
Kuntal Ghosh <kuntalghosh.2007@gmail.com>, Liudmila Mantrova <l.mantrova@postgrespro.ru>,
Thomas Munro <thomas.munro@gmail.com>, Andrey Borodin <x4mmm@yandex-team.ru>, David Steele <david@pgmasters.net>, Andres Freund <andres@anarazel.de>,
PostgreSQL-development <pgsql-hackers@postgresql.org>, Dmitry Dolgov <9erthalion6@gmail.com>, vladimirlesk@yandex-team.ru, dsarafan@yandex-team.ru
Date: 2020-06-07T19:05:03Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Move frontend-side archive APIs from src/common/ to src/fe_utils/
- 8d8b89266ca0 13.0 landed
- a3b2bf1fe7ce 14.0 landed
-
Add -c/--restore-target-wal to pg_rewind
- a7e8ece41cf7 13.0 landed
-
Move routine definitions of xlogarchive.c to a new header file
- 616ae3d2b056 13.0 landed
-
Move routine building restore_command to src/common/
- e09ad07b21a2 13.0 landed
-
Integrate recovery.conf into postgresql.conf
- 2dedf4d9a899 12.0 cited
Hi! On Sat, Jun 6, 2020 at 8:49 PM Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote: > > On 2020-03-31 08:48, Michael Paquier wrote: > > On Mon, Mar 30, 2020 at 05:00:01PM +0300, Alexey Kondratov wrote: > >> What do think about adding following sanity check into xlogarchive.c? > >> > >> +#ifdef FRONTEND > >> +#error "This file is not expected to be compiled for frontend code" > >> +#endif > >> > >> It would prevent someone from adding typedefs and any other common > >> definitions into xlogarchive.h in the future, leading to the accidental > >> inclusion of both xlogarchive.h and fe_archive.h in the same time. > > I don't see much the point as this would fail to compile anyway, and > > that's not project-style. Note that we have already a clear > > separation here between the backend and the frontend code here as > > xlogarchive.h is backend-only and fe_archive.h is frontend-only. > > Why is fe_archive.c in src/common/ and not in src/fe_utils/? It is not > "common" to frontend and backend. Yep, this seems wrong to me. I can propose following file rename. src/common/fe_archive.c => src/fe_utils/archive.c include/common/fe_archive.h => include/fe_utils/archive.h > It actually defines functions that clash with functions in the backend, > so this seems doubly wrong. Let's have frontend version of RestoreArchivedFile() renamed as well. What about RestoreArchivedFileFrontend()? ------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company