| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Leonardo Francalanci <m_lists(at)yahoo(dot)it> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: switch UNLOGGED to LOGGED |
| Date: | 2011-05-18 15:52:16 |
| Message-ID: | 20110518155216.GA29843@tornado.gateway.2wire.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 18, 2011 at 04:02:59PM +0100, Leonardo Francalanci wrote:
> > By the time the startup process
> > releases the AccessExclusiveLock acquired by the proposed
> > UNLOGGED -> normal conversion process, that relfilenode
> > needs to be either fully copied or unlinked all over again.
> > (Alternately, find some other way to make sure queries don't
> > read the half-copied file.)
>
> About this issue: how are AccessExclusiveLocks released on
> the standby when the master crashes?
I assume those locks remain. It wouldn't be safe to release them; a master
crash is just one kind of WAL receipt latency.
When you promote the standby, though, ShutdownRecoveryTransactionEnvironment()
releases the locks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2011-05-18 16:12:48 | Re: Use of access(X_OK) check in pg_upgrade |
| Previous Message | Bruce Momjian | 2011-05-18 15:41:51 | Use of access(X_OK) check in pg_upgrade |