Re: findDependentObjects() mutual exclusion vs. MVCC catalog scans

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: findDependentObjects() mutual exclusion vs. MVCC catalog scans
Date: 2013-07-16 15:35:48
Message-ID: 11946.1373988948@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Jul 16, 2013 at 9:50 AM, Noah Misch <noah(at)leadboat(dot)com> wrote:
>> Let's fix this by having systable_recheck_tuple() acquire a fresh catalog MVCC
>> snapshot and recheck against that. I believe it would also be fully safe to
>> use SnapshotNow here; however, I'm assuming we would otherwise manage to
>> remove SnapshotNow entirely.

I agree with Robert's comments, and in addition suggest that this code
needs a comment about why it's safe to use the snapshot without doing
RegisterSnapshot or equivalent.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2013-07-16 15:39:55 Re: make dist error
Previous Message Robert Haas 2013-07-16 15:27:02 Re: findDependentObjects() mutual exclusion vs. MVCC catalog scans