From: Jim C. Nasby <jim@nasby.net>
To: Jerry Sievers <jerry@jerrysievers.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Manual sys catalog constraint setup to avoid downtime?
Date: Thu, 9 Nov 2006 01:11:19 -0600
Message-ID: <20061109071118.GF90133@nasby.net> (raw)
In-Reply-To: <m3lkmnfdil.fsf@homie.jerrysievers.com>
References: <m3lkmnfdil.fsf@homie.jerrysievers.com>
On Tue, Nov 07, 2006 at 11:05:38AM -0500, Jerry Sievers wrote:
> Admins; this is (I assume) a not uncommon scenario).
>
> Suppose you are managing a BIG ugly DB that's in 24x7 production and
> desperately in need of constraints of all types.
>
> (Of course, you inherited this piece of crap and the irresponsible
> designers are long gone :-)
>
> You have verified that the application now honors the new constraints
> because on your R&D DBs, the constraints are in place and no
> constraint violations are occuring.
>
> You can't however get business to sign off on proper constraint
> addition via ALTER TABLE because the tables are huge and this locks
> out concurrent activity for several hours.
>
> My question;
>
> Have any of you setup the constraints by doing manual catalog updates
> and later (or maybe never), gone back and cleaned up the
> non-conforming data using small batch updates or deletes?
>
> Frobing of pg_constraint and pg_depend (at least) would be required.
>
> I'm wondering what non-obvious pitfalls exist here?
>
> Comments?
Use the source, luke!
Hmmm... interesting problem. For some constraints, I think you could
probably handle things pretty well once we have non-blocking index
creation (did that get into 8.2?). I guess the real key there would be
if the constraint creation code will use indexes when checking the
constraints. This would be especially useful for generic CHECK
constraints... if you build an index that has a WHERE clause that
matches the proposed constraint, the backend could just look to see if
there are any entries in the index. If there aren't, you're good to go.
In the meantime, I suggest using triggers to enforce your constraints,
since you can create one without verifying the underlying data.
--
Jim Nasby jim@nasby.net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: jim@nasby.net, jerry@jerrysievers.com
Subject: Re: Manual sys catalog constraint setup to avoid downtime?
In-Reply-To: <20061109071118.GF90133@nasby.net>
References: <m3lkmnfdil.fsf@homie.jerrysievers.com> <20061109071118.GF90133@nasby.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox