From: | "Dawid Kuroczko" <qnex42(at)gmail(dot)com> |
---|---|
To: | Decibel! <decibel(at)decibel(dot)org> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Lazy constraints / defaults |
Date: | 2008-03-20 18:51:56 |
Message-ID: | 758d5e7f0803201151y39307f03r1dd1e0389b0ec577@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Mar 20, 2008 at 4:56 PM, Decibel! <decibel(at)decibel(dot)org> wrote:
> This would be very useful for me, and would satisfy the OP's request.
>
> Can we get a TODO?
If you feel adventureous you may UPDATE catalog constrains directly,
which will work more or less as "enforce, don't validate, don't lock". ;-)
Worked for me. ;-) I deliberately don't say where to update. ;-)
But for a TODO feature it should LOUDLY INDICATE that given
constraint is NOT VALIDATED, After all, PostgreSQL is famous
for its high ACIDity standards. [ And event then... ;) ]
Regards,
Dawid
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mason | 2008-03-20 19:23:32 | writing a MIN(RECORD) aggregate |
Previous Message | Tom Lane | 2008-03-20 18:03:11 | Re: [PATCHES] [GENERAL] Empty arrays with ARRAY[] |