| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: XLogArchivingActive |
| Date: | 2006-05-26 13:23:22 |
| Message-ID: | 25165.1148649802@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andreas Pflug <pgadmin(at)pse-consulting(dot)de> writes:
> Tom Lane wrote:
>> I'm not sure you can expect that to work. The system is not built to
>> guarantee instantaneous response to mode changes like that.
> Um, as long as xlog writing stops immediate recycling when
> pg_start_backup is executed everything should be fine, since archived
> logs are not expected to be present until pg_stop_backup is done.
Wrong. You forgot about all the *other* behaviors that change depending
on XLogArchivingActive, like whether CREATE INDEX gets archived or
just fsync'd. I don't think it makes sense for CREATE INDEX to change
that behavior in midstream, even assuming that it noticed the flag
change instantly.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2006-05-26 13:45:54 | Re: max(*) |
| Previous Message | Martijn van Oosterhout | 2006-05-26 13:03:15 | Re: timezones to own config file |