Re: pg_start_backup and pg_stop_backup Re: Re: [COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon correct
| От | Robert Haas | 
|---|---|
| Тема | Re: pg_start_backup and pg_stop_backup Re: Re: [COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon correct | 
| Дата | |
| Msg-id | AANLkTimDvFOc8sHkE_P36wHdynmPmyWtehlr6C0KsfYE@mail.gmail.com обсуждение исходный текст | 
| Ответ на | Re: pg_start_backup and pg_stop_backup Re: Re: [COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon correct (Bruce Momjian <bruce@momjian.us>) | 
| Ответы | Re: pg_start_backup and pg_stop_backup Re: Re:
 [COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon
 correct | 
| Список | pgsql-hackers | 
On Fri, Apr 30, 2010 at 12:22 PM, Bruce Momjian <bruce@momjian.us> wrote: > Tom Lane wrote: >> Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes: >> > Tom Lane wrote: >> >> 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. >> >> > I wasn't really thinking of this use case, but you could set >> > wal_keep_segments "high enough". >> >> Ah. Okay, that seems like a workable approach, at least for people with >> reasonably predictable WAL loads. We could certainly improve on it >> later to make it more bulletproof, but it's usable now --- if we relax >> the error checks. >> >> (wal_keep_segments can be changed without restarting, right?) > > Should we allow -1 to mean "keep all segments"? If that's what you want to do, use archive_mode. ...Robert
В списке pgsql-hackers по дате отправления: