| From: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | depstein <depstein(at)alliedtesting(dot)com>, mmoncure <mmoncure(at)gmail(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Problems with ENUM type manipulation in 9.1 |
| Date: | 2011-09-28 15:40:37 |
| Message-ID: | CAK3UJRF3r69tXQaLxPQq-TPL_CZekbxX0nboKxsac1biXsZupg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Sep 28, 2011 at 10:51 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Excerpts from depstein's message of mié sep 28 07:21:17 -0300 2011:
>> Anyway, the procedure that we used (based on
>> http://en.dklab.ru/lib/dklab_postgresql_enum/) does the necessary
>> checks before removing enum values.
Not exactly; that code is rife with race conditions. For instance, how
does the "Check data references" loop ensure that previously-checked
tables don't get a new row containing the forbidden enum_elem before
the function is finished?
Josh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-09-28 15:43:26 | Re: BUG #6231: weird to_timestamp behaviour with out of range values |
| Previous Message | Henk Enting | 2011-09-28 14:55:57 | BUG #6231: weird to_timestamp behaviour with out of range values |