| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> |
| Cc: | PG Docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: VALIDATE CONSTRAINT |
| Date: | 2013-09-02 14:50:09 |
| Message-ID: | 15351.1378133409@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> writes:
> Is there a reason, besides simple oversight, that commit
> 073d7cb513f5de44530f4bdbaaa4b5d4cce5f984 was not backpatched?
> I think it needs to be.
AFAICS, it was.
Author: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Branch: master [073d7cb51] 2013-06-18 12:09:39 +0100
Branch: REL9_3_STABLE [0ae1bf8c1] 2013-06-18 12:10:10 +0100
Branch: REL9_2_STABLE [20a562f91] 2013-06-18 12:00:32 +0100
Branch: REL9_1_STABLE [be039d4b2] 2013-06-18 12:05:48 +0100
Fix docs on lock level for ALTER TABLE VALIDATE
ALTER TABLE .. VALIDATE CONSTRAINT previously
gave incorrect details about lock levels and
therefore incomplete reasons to use the option.
Initial bug report and fix from Marko Tiikkaja
Reworded by me to include comments by Kevin Grittner
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2013-09-02 15:32:40 | Re: VALIDATE CONSTRAINT |
| Previous Message | Vik Fearing | 2013-09-02 08:25:25 | VALIDATE CONSTRAINT |