Reduce lock level for ALTER TABLE ... ADD CHECK .. NOT VALID - Mailing list pgsql-hackers

From Simon Riggs
Subject Reduce lock level for ALTER TABLE ... ADD CHECK .. NOT VALID
Date
Msg-id CANbhV-EUvRNs1zMdkXFeBg=Bqn8v0bm_qn3orrBwAJa3gZq6kA@mail.gmail.com
Whole thread Raw
Responses Re: Reduce lock level for ALTER TABLE ... ADD CHECK .. NOT VALID  (Greg Sabino Mullane <htamfids@gmail.com>)
Re: Reduce lock level for ALTER TABLE ... ADD CHECK .. NOT VALID  (John Naylor <john.naylor@enterprisedb.com>)
Re: Reduce lock level for ALTER TABLE ... ADD CHECK .. NOT VALID  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
897795240cfaaed724af2f53ed2c50c9862f951f forgot to reduce the lock
level for CHECK constraints when allowing them to be NOT VALID.

This is simple and safe, since check constraints are not used in
planning until validated.

-- 
Simon Riggs                http://www.EnterpriseDB.com/

Attachment

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: decoupling table and index vacuum
Next
From: "tanghy.fnst@fujitsu.com"
Date:
Subject: RE: Support tab completion for upper character inputs in psql