Re: why does enum_endpoint call GetTransactionSnapshot()?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: why does enum_endpoint call GetTransactionSnapshot()?
Date: 2015-02-14 22:12:42
Message-ID: 13533.1423951962@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:
> I think this is probably a holdover from before the death of
> SnapshotNow, and that we should just pass NULL to
> systable_beginscan_ordered() here, the same as we do for other catalog
> accesses. Barring objections, I'll go make that change.

Seems reasonable to me, but why are you only looking at that one and
not the identical code in enum_range_internal()?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-02-14 22:29:43 Re: why does enum_endpoint call GetTransactionSnapshot()?
Previous Message Heikki Linnakangas 2015-02-14 22:06:48 Re: INSERT ... ON CONFLICT {UPDATE | IGNORE} 2.0