| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hot standby, dropping a tablespace |
| Date: | 2009-01-25 09:04:01 |
| Message-ID: | 1232874241.2327.1431.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 2009-01-24 at 21:58 +0200, Heikki Linnakangas wrote:
> When replaying a DROP TABLE SPACE, you first try to remove the
> directory, and if that fails, you assume that it's because it's in use
> as a temp tablespace in a read-only transaction.
That sounds like you think there another conclusion?
> You then call
> ResolveRecoveryConflictWithVirtualXIDs to kill such transactions, and
> try removing the directory again. But
> ResolveRecoveryConflictWithVirtualXIDs doesn't wait for the target
> transaction to die anymore (or at least it shouldn't, as we discussed
> earlier), so that doesn't work AFAICS.
The FATAL errors inflicted should be fairly quick to take effect, so
waiting should not be a problem. We can make waiting for FATAL errors
the standard response.
> One quick work around would be to simply not respect temp_tablespace
> during recovery...
No, don't think that's acceptable.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-01-25 09:28:42 | Re: Hot standby, dropping a tablespace |
| Previous Message | Guillaume Smet | 2009-01-25 08:41:14 | Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle |