Re: [PATCHES] Eliminating phase 3 requirement for varlen increases via ALTER COLUMN - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: [PATCHES] Eliminating phase 3 requirement for varlen increases via ALTER COLUMN
Date
Msg-id 877iym3j5w.fsf@enterprisedb.com
Whole thread Raw
In response to Re: [PATCHES] Eliminating phase 3 requirement for varlen increases via ALTER COLUMN  ("Jonah H. Harris" <jonah.harris@gmail.com>)
Responses Re: [PATCHES] Eliminating phase 3 requirement for varlen increases via ALTER COLUMN  ("Jonah H. Harris" <jonah.harris@gmail.com>)
List pgsql-hackers
"Jonah H. Harris" <jonah.harris@gmail.com> writes:

> On 10/26/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> This makes some really quite unacceptable assumptions about
>> the meaning and encoding of typmod ...
>
> True, so VARCHAR seems like the only one?  That's the only one I've
> really encountered in the field on a fairly regular basis.

I think what you want is to add a new method entry in pg_type to allow a type
to declare a method to tell you whether a change is work-free or not. Then any
type, even user-defined types, can allow some changes to be work-free and some
not without exposing any implementation details outside the type.

--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: "Andrej Ricnik-Bay"
Date:
Subject: Re: plperl/plperlu interaction
Next
From: Chris Campbell
Date:
Subject: Deadlock with pg_dump?