| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Zdenek Kotala <Zdenek(dot)Kotala(at)sun(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Deadlock in vacuum (check fails) |
| Date: | 2010-02-01 15:11:29 |
| Message-ID: | 19782.1265037089@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:
> Does this create a problem combined with the plan to allow the new
> VACUUM FULL to rewrite system tables? From my brief scan it sounds
> like the only reason there's no race condition here is that previously
> the oid of system tables couldn't change out from under
> load_critical_index.
Their OIDs will never change, so I don't see an issue. Locks are taken
on OIDs not relfilenodes, so a relocation doesn't break locking. If
it did we'd already have a problem with relocating user tables.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-02-01 15:15:39 | Re: Hot Standby and VACUUM FULL |
| Previous Message | Tom Lane | 2010-02-01 15:07:49 | Re: Hot Standby and VACUUM FULL |