Greg Stark wrote:
> On Tue, Dec 8, 2009 at 8:30 AM, Heikki Linnakangas
> <heikki.linnakangas@enterprisedb.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
