Re: ALTER TYPE 3: add facility to identify further no-work cases - Mailing list pgsql-hackers

From Robert Haas
Subject Re: ALTER TYPE 3: add facility to identify further no-work cases
Date
Msg-id AANLkTinX6uu0YBcDdPavFNLHrQQbgRK_3i96VUabtPqW@mail.gmail.com
Whole thread Raw
In response to Re: ALTER TYPE 3: add facility to identify further no-work cases  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Jan 26, 2011 at 7:44 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> But how often do those really come up?  And do you really save that
> much?  The table still has to be locked against other users, so you're
> still down, and you're still doing all the reads and computation.  I
> don't deny that saving the writes is worth something; I just don't agree
> that it's worth the development and maintenance effort that such a wart
> is going to cost us.  User-exposed features are *expensive*.

I would think that text -> [something that's still a varlena but with
tighter validation] would be quite common.

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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: ALTER TYPE 3: add facility to identify further no-work cases
Next
From: Noah Misch
Date:
Subject: Re: ALTER TYPE 3: add facility to identify further no-work cases