Re: [BUGS] BUG #14825: enum type: unsafe use?

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: balazs(at)obiserver(dot)hu, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #14825: enum type: unsafe use?
Date: 2017-09-23 17:48:23
Message-ID: 69cf0c50-949d-047e-24f6-aeb0871aac67@2ndQuadrant.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On 09/23/2017 11:16 AM, Tom Lane wrote:
> Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
>
>>> The immediate question is do we care to design/implement such a thing
>>> post-RC1. I'd have to vote "no". I think the most prudent thing to
>>> do is revert 15bc038f9 and then have another go at it during the v11
>>> cycle.
>> Sadly I agree. We've made decisions like this in the past, and I have
>> generally been supportive of them. I think this is the first time I have
>> been on the receiving end of one so late in the process :-(
> Unless you want to try writing a patch for this in the next day or two,
> I think we have to do that. But now that I see the plan clearly, maybe
> we could get away with a post-RC1 fix.

OK, I'll give it a shot.

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-09-23 18:00:56 Re: BUG #14825: enum type: unsafe use?
Previous Message Tom Lane 2017-09-23 16:26:08 Re: BUG #14826: Malformed array dimensions for empty arrays in return column "lexemes" of ts_debug()

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-09-23 18:00:56 Re: BUG #14825: enum type: unsafe use?
Previous Message Bossart, Nathan 2017-09-23 17:40:12 Re: Rethinking autovacuum.c memory handling