Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UkiRt-0006Ru-VI for pgsql-docs@arkaria.postgresql.org; Thu, 06 Jun 2013 22:14:26 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UkiRt-0004w2-Fu for pgsql-docs@arkaria.postgresql.org; Thu, 06 Jun 2013 22:14:25 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Ujzjr-0004Y5-2W for pgsql-docs@postgresql.org; Tue, 04 Jun 2013 22:29:59 +0000 Received: from mail-lb0-f181.google.com ([209.85.217.181]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Ujzjo-0005ov-Ix for pgsql-docs@postgresql.org; Tue, 04 Jun 2013 22:29:58 +0000 Received: by mail-lb0-f181.google.com with SMTP id 13so1248384lba.12 for ; Tue, 04 Jun 2013 15:29:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=zv01jzTW2QYBhlIfpfRrZhEQ3VQ/+3Vlwwr23XnSyY4=; b=kWpJYZnXOe2kP2eiJpDFxvlcCNQzvv1cYqkyh8IlcuElT/bkSpjLruGZN18FfhI3A/ CqWnrttNI/xQNJKVYxOU/ta3FCH1EDhPCj48zMpt71eh2qr+WGS+Iv+FkoS0gEB1xfn3 TmVrnnsLiZLceQr9Gmmezh7rGIINLf7vqkS+njCb3GWyUCbGSQqrLuUaM94PrL27ELuH HAq2DqSfL3zmpDJkczJ6lbxTS9UvbWlKfD0WEpUVeemPs3Nqvg39nyWpL83LiZ4HcDc3 Uswh9qUExeD4p1PJEcz36YHeqOnKYk7CYVCMDsRpKKQe7ZzjqFggn6Dgj1ASw2fQO+V2 Je9g== X-Received: by 10.112.129.198 with SMTP id ny6mr2460881lbb.113.1370384994531; Tue, 04 Jun 2013 15:29:54 -0700 (PDT) Received: from [192.168.1.66] (81-237-193-137-no16.tbcn.telia.com. [81.237.193.137]) by mx.google.com with ESMTPSA id p6sm17012455lbv.15.2013.06.04.15.29.52 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 04 Jun 2013 15:29:53 -0700 (PDT) Message-ID: <51AE6A55.702@joh.to> Date: Wed, 05 Jun 2013 00:29:41 +0200 From: Marko Tiikkaja User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Kevin Grittner CC: "pgsql-docs@postgresql.org" Subject: Re: ALTER TABLE lock level References: <51A37A72.5000203@joh.to> <51A89BAE.6000704@joh.to> <1370173658.22143.YahooMailNeo@web162902.mail.bf1.yahoo.com> In-Reply-To: <1370173658.22143.YahooMailNeo@web162902.mail.bf1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQlRsT/7sGE+puxijplTeoiidW/bsaTlrgxv2Q2QXZl1Y7UOZEuzibhMVnDScNjDNCOXz96N X-Pg-Spam-Score: 0.1 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org 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