Re: XX000: enum value 117721 not found in cache for enum enumcrash - Mailing list pgsql-hackers

From Robert Haas
Subject Re: XX000: enum value 117721 not found in cache for enum enumcrash
Date
Msg-id 798991EA-747A-4456-8002-3C69476CAE40@gmail.com
Whole thread Raw
In response to Re: XX000: enum value 117721 not found in cache for enum enumcrash  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: XX000: enum value 117721 not found in cache for enum enumcrash  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Jul 2, 2012, at 12:04 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Jul 1, 2012, at 4:18 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> However, I'm a bit worried by the "if (!FirstSnapshotSet)" restriction
>> in GetLatestSnapshot.  Are we sure that enum comparisons could never
>> happen without a snapshot already being set?  What's the point of
>> throwing an error there anyway, as opposed to letting it redirect to
>> GetTransactionSnapshot?
>
> I don't know whether it should set the transaction snapshot or just r

Argh, sorry.

...or just return a current snapshot, and I also don't know whether it needs to be changed because of this; but I agree
withchanging it. Erroring out always seemed kind of pointless to me... 

...Robert

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: XX000: enum value 117721 not found in cache for enum enumcrash
Next
From: Tom Lane
Date:
Subject: Re: XX000: enum value 117721 not found in cache for enum enumcrash