| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Rod Taylor" <rbt(at)rbt(dot)ca>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "PostgreSQL Development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: add column .. default |
| Date: | 2003-06-20 01:22:36 |
| Message-ID: | 003d01c336ca$6f630580$2800a8c0@mars |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> There is no alternative, unless you want the command to be
> non-roll-back-able.
Well, you can do a cluster-type table duplication...
> > Someone can
> > make it more efficient in regards to constraint checks, etc. in the
> > future if they want -- I don't intend to.
>
> It'd be nice if you at least ensure that all the constraints are checked
> in a single pass over the table (not one per constraint). Right offhand
> I do not see why they couldn't be checked in the same pass that does the
> UPDATE. For extra credit, detect that the default expression is
> immutable or stable, and do the checks *once* not once per row.
And check domain constraints...?
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-06-20 01:23:13 | Re: src/bin/scripts seems a bit of a misnomer now |
| Previous Message | Christopher Kings-Lynne | 2003-06-20 01:21:52 | Re: allowed user/db variables |