Re: [Patch] pg_rewind: options to use restore_command fromrecovery.conf or command line
От | Alvaro Herrera |
---|---|
Тема | Re: [Patch] pg_rewind: options to use restore_command fromrecovery.conf or command line |
Дата | |
Msg-id | 20181022171907.ri2tkqtt7n6jm4dh@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: [Patch] pg_rewind: options to use restore_command fromrecovery.conf or command line (Alexey Kondratov <a.kondratov@postgrespro.ru>) |
Ответы |
Re: [Patch] pg_rewind: options to use restore_command fromrecovery.conf or command line
Re: [Patch] pg_rewind: options to use restore_command fromrecovery.conf or command line |
Список | pgsql-hackers |
On 2018-Oct-22, Alexey Kondratov wrote: > > I didn't actually try patch yet, but the idea seems interesting. Will > > you add it to the commitfest? > I am willing to add it to the November commitfest, but I have some concerns > regarding frontend version of GUC parser. Probably, it is possible to > refactor guc-file.l to use it on both front- and backend. However, it > requires usage of IFDEF and mocking up ereport for frontend, which is a bit > ugly. Hmm, I remember we had a project to have a new postmaster option that would report the value of some GUC option, so instead of parsing the file in the frontend, you'd invoke the backend to do the parsing. But I don't know what became of that ... I don't see it in the postmaster --help output. Of course, recovery.conf options are not GUCs either ... that's another pending patch. We do have some backend-mock for frontends, e.g. in pg_waldump; plus palloc is already implemented in libpgcommon. I don't know if what you need to compile the lexer is a project much bigger than finishing the other two patches I mention. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: