Re: odd buildfarm failure - "pg_ctl: control file appears to be corrupt"
От | Thomas Munro |
---|---|
Тема | Re: odd buildfarm failure - "pg_ctl: control file appears to be corrupt" |
Дата | |
Msg-id | CA+hUKG+4FSkHV5ftUJmA8CjVWWuMV2GM6GfCbsZHFz0RYQwM0Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: odd buildfarm failure - "pg_ctl: control file appears to be corrupt" ("Anton A. Melnikov" <aamelnikov@inbox.ru>) |
Ответы |
Re: odd buildfarm failure - "pg_ctl: control file appears to be corrupt"
|
Список | pgsql-hackers |
On Wed, Mar 8, 2023 at 4:43 PM Anton A. Melnikov <aamelnikov@inbox.ru> wrote: > On 04.03.2023 00:39, Thomas Munro wrote: > > Could we make better use of the safe copy that we have in the log? > > Then the pg_backup_start() subproblem would disappear. Conceptually, > > that'd be just like the way we use FPI for data pages copied during a > > backup. I'm not sure about any of that, though, it's just an idea, > > not tested. > > Sorry, i didn't understand the question about log. Would you explain me > please what kind of log did you mention and where can i look this > safe copy creation in the code? Sorry, I was confused; please ignore that part. We don't have a copy of the control file anywhere else. (Perhaps we should, but that could be a separate topic.)
В списке pgsql-hackers по дате отправления: