From: | Leonardo Francalanci <m_lists(at)yahoo(dot)it> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: switch UNLOGGED to LOGGED |
Date: | 2011-04-11 10:41:18 |
Message-ID: | 826909.74063.qm@web29018.mail.ird.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > But re-reading it, I don't understand: what's the difference in creating
> > a new "regular" table and crashing before emitting the abort record,
> > and converting an unlogged table to logged and crashing before
> > emitting the abort record? How do the standby servers handle a
> > "CREATE TABLE" followed by a ROLLBACK if the master crashes
> > before writing the abort record? I thought that too would "leave a
> > stray file around on a standby".
>
> I've been thinking about the same thing. And AFAICS, your analysis is
> correct, though there may be some angle to it I'm not seeing.
Anyone else? I would like to know if what I'm trying to do is, in fact,
possible... otherwise starting with thewal_level=minimal case first
will be wasted effort in case the other cases can't be integrated
somehow...
Leonardo
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2011-04-11 10:58:40 | Re: SSI bug? |
Previous Message | Albert Cervera i Areny | 2011-04-11 10:34:03 | developer.postgresql.org down |