| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER TABLE TODO items |
| Date: | 2004-05-05 19:45:39 |
| Message-ID: | 40994463.1020401@archonet.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>
>>Wow, you can reference different column as part of the alter column.
>
>
> Yeah, the USING is actually any arbitrary expression over the old table
> row. (Getting that to work was a tad tricky...) So you can view this
> as a full-table UPDATE operation that folds in possible column type changes.
Does that mean I'll want to disable triggers while I do this? Actually,
if the structure's changing I presume I'll want to drop/recreate my
triggers anyway (even if they get reparsed like view definitions).
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-05-05 19:50:02 | Re: ALTER TABLE TODO items |
| Previous Message | Tom Lane | 2004-05-05 17:59:04 | Re: ALTER TABLE TODO items |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-05-05 19:50:02 | Re: ALTER TABLE TODO items |
| Previous Message | Steve Atkins | 2004-05-05 19:36:30 | Re: PostgreSQL pre-fork speedup |