From: Marko Tiikkaja <marko@joh.to>
To: Kevin Grittner <kgrittn@ymail.com>
Cc: pgsql-docs@postgresql.org <pgsql-docs@postgresql.org>
Subject: Re: ALTER TABLE lock level
Date: Wed, 05 Jun 2013 00:29:41 +0200
Message-ID: <51AE6A55.702@joh.to> (raw)
In-Reply-To: <1370173658.22143.YahooMailNeo@web162902.mail.bf1.yahoo.com>
References: <51A37A72.5000203@joh.to>
<51A89BAE.6000704@joh.to>
<1370173658.22143.YahooMailNeo@web162902.mail.bf1.yahoo.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
On 02/06/2013 13:47, Kevin Grittner wrote:
> That's good as far as it goes, but there's another major reason for
> wanting the capability. There are cases where, due to dirty
> converted data or late recognition of the need for a constraint
> there is existing data which violates the constraint. Being able
> to add a constraint to protect against creating additional bad data
> before all the existing problems are cleaned up can be valuable.
Yeah, that's a valid use case.
Anyway, you seem to know more about this than I do and your English is
better, so I'll leave it up to you. I just hope we can get this change
into the next minor release so I'd be the last person to suffer from the
misinformation that's currently in the documentation.
Regards,
Marko Tiikkaja
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
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 using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: marko@joh.to, kgrittn@ymail.com
Subject: Re: ALTER TABLE lock level
In-Reply-To: <51AE6A55.702@joh.to>
* 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