Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Eliminating phase 3 requirement for varlen increases via ALTER COLUMN

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] Eliminating phase 3 requirement for varlen increases via ALTER COLUMN
Date: 2006-10-26 20:40:27
Message-ID: 877iym3j5w.fsf@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
"Jonah H. Harris" <jonah(dot)harris(at)gmail(dot)com> writes:

> On 10/26/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Andrej Ricnik-BayDate: 2006-10-26 20:42:40
Subject: Re: plperl/plperlu interaction
Previous:From: Josh BerkusDate: 2006-10-26 20:20:32
Subject: Re: plperl/plperlu interaction

pgsql-patches by date

Next:From: Chris CampbellDate: 2006-10-26 20:45:02
Subject: Deadlock with pg_dump?
Previous:From: Tom LaneDate: 2006-10-26 20:00:49
Subject: Re: Eliminating phase 3 requirement for varlen increases via ALTER COLUMN

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group