| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Streaming replication, some small issues |
| Date: | 2009-12-08 12:05:03 |
| Message-ID: | 4B1E40EF.2020405@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Stark wrote:
> On Tue, Dec 8, 2009 at 8:30 AM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> - It's possible to shut down master, change max_wal_senders to 0,
>> restart and do an operation like CLUSTER which then skips WAL-logging.
>> Then shutdown, change max_wal_senders back to non-zero. All this while
>> the standby is running. Leads to a corrupt standby.
>
> The same thing is possible with archived logs as well, no?
Yeah, I think you're right.
> I suspect we should have a WAL record to say "unlogged operation
> performed here" which a standby database would recognize and throw a
> large warning up.
+1. Seems like a very simple solution.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-12-08 12:16:06 | Re: questions about concurrency control in Postgresql |
| Previous Message | Greg Stark | 2009-12-08 11:54:58 | Re: Streaming replication, some small issues |