| From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
|---|---|
| To: | "Gregory Stark" <stark(at)enterprisedb(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 21:16:19 |
| Message-ID: | 36e682920610261416x389055e3xdc421ef1fff27184@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On 10/26/06, Gregory Stark <stark(at)enterprisedb(dot)com> wrote:
> 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.
Seems like too much work for a fairly simple use-case.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation | fax: 732.331.1301
33 Wood Ave S, 2nd Floor | jharris(at)enterprisedb(dot)com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-10-26 21:21:26 | Re: Deadlock with pg_dump? |
| Previous Message | Andrew Dunstan | 2006-10-26 20:58:21 | Re: plperl/plperlu interaction |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-10-26 21:21:26 | Re: Deadlock with pg_dump? |
| Previous Message | Chris Campbell | 2006-10-26 20:45:02 | Deadlock with pg_dump? |