| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Hot Standby and VACUUM FULL |
| Date: | 2010-02-01 15:07:49 |
| Message-ID: | 19692.1265036869@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> On Mon, Feb 1, 2010 at 8:54 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>>> Disallow catalog relocation inside subtransactions, to avoid having
>>> to handle subxact abort effects on the local-map-changes state.
>>> This could be implemented if desired, but doesn't seem worth it
>>> at least in first pass.
>>
>> Agreed, not needed for emergency maintenance actions like this.
> Note that this would mean it will never work if you have psql's
> ROLLBACK_ON_ERROR set.
VACUUM has always failed in such a case, so I don't see this as a
showstopper.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-02-01 15:11:29 | Re: Deadlock in vacuum (check fails) |
| Previous Message | Tom Lane | 2010-02-01 15:06:17 | Re: Hot Standby and VACUUM FULL |