Re: pg_start_backup and pg_stop_backup Re: Re: [COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon correct
От | Tom Lane |
---|---|
Тема | Re: pg_start_backup and pg_stop_backup Re: Re: [COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon correct |
Дата | |
Msg-id | 3478.1272477227@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: pg_start_backup and pg_stop_backup Re: Re: [COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon correct (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
Re: pg_start_backup and pg_stop_backup Re: Re: [COMMITTERS]
pgsql: Make CheckRequiredParameterValues() depend upon correct
Re: pg_start_backup and pg_stop_backup Re: Re: [COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon correct |
Список | pgsql-hackers |
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes: > Well, it would be nice to allow using pg_start_backup() on the primary > when streaming replication is enabled, even if archiving isn't. > Otherwise the only way to get the base backup for the standby is to shut > down primary first, or use filesystem snapshot etc. I think I must be missing something: exactly how would you fire up a new standby from such a base backup, if you weren't running archiving? If you aren't archiving then there's no guarantee that you'll still have a continuous WAL series starting from the start of the backup. IOW I think that the requirement in pg_start_backup shouldn't be relaxed without some more thought/work. regards, tom lane
В списке pgsql-hackers по дате отправления: