Re: WIP: extensible enums - Mailing list pgsql-hackers

From Tom Lane
Subject Re: WIP: extensible enums
Date
Msg-id 8554.1287326331@sss.pgh.pa.us
Whole thread Raw
In response to Re: WIP: extensible enums  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: WIP: extensible enums  (Dean Rasheed <dean.a.rasheed@gmail.com>)
Re: WIP: extensible enums  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> On 10/17/2010 05:30 AM, Dean Rasheed wrote:
>> I just thought of another corner case, which can lead to a crash. The
>> comparison code assumes that the number of elements in the enumeration
>> is constant during a query, but that's not necessarily the case.
>> ...
>> Of course that's a pathalogical example, but we should protect against
>> it, preferrably without compromising performance in more normal cases.

> Yeah, good point. But how do we manage that?

Why is it crashing?  I can see that this sort of thing might lead to
nonsensical answers, but a crash is harder to understand.
        regards, tom "haven't read the patch" lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: WIP: extensible enums
Next
From: Magnus Hagander
Date:
Subject: Re: Foreign Visual Studio builds