Re: ALTER TYPE 3: add facility to identify further no-work cases

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: ALTER TYPE 3: add facility to identify further no-work cases
Date: 2011-01-29 11:06:20
Message-ID: AANLkTin3HYvQ_g17F7dwx4izAmjAVfmtHBexoQUXGxSv@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jan 29, 2011 at 3:26 AM, Noah Misch <noah(at)leadboat(dot)com> wrote:
> One other thing: #7 does not depend on #3,4,5,6 or any design problems raised
> thus far, so there's no need to treat it the same as that group.

Well, if you want to post an updated patch that's independent of the
rest of the series, I guess you can... but I think the chances of that
getting applied for this release are pretty much zero. That patch
relies on some subtle changes to the contract implied by an operator
family and what looks at first blush like a lot of grotty hackery. I
can't get very excited about spending a lot of time on that right now,
especially given the amount of difficulty we've had reaching a meeting
of the minds on cases that don't have those problems.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2011-01-29 11:12:55 Snapshots no longer build
Previous Message Robert Haas 2011-01-29 10:53:29 Re: ALTER TYPE 3: add facility to identify further no-work cases