| From: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: NOT VALID for Unique Indexes |
| Date: | 2021-02-26 09:29:05 |
| Message-ID: | CANbhV-GPmz7o3J4niod4TbCQciu=g9FwCVn0pKNDdq_zr-Om=g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 18, 2021 at 12:34 AM David Fetter <david(at)fetter(dot)org> wrote:
>
> On Thu, Jan 14, 2021 at 04:22:17PM +0000, Simon Riggs wrote:
> > As you may be aware the NOT VALID qualifier currently only applies to
> > CHECK and FK constraints, but not yet to unique indexes. I have had
> > customer requests to change that.
>
> This is a great feature!
>
> Not exactly on point with this, but in a pretty closely related
> context, is there some way we could give people the ability to declare
> at their peril that a constraint is valid without incurring the full
> scan that VALIDATE currently does? This is currently doable by
> fiddling directly with the catalog, which operation is broadly more
> dangerous and ill-advised.
That is what NOT VALID allows, but it can't be relied on for optimization.
--
Simon Riggs http://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2021-02-26 09:36:34 | Re: NOT VALID for Unique Indexes |
| Previous Message | tanghy.fnst@fujitsu.com | 2021-02-26 09:23:55 | RE: Parallel INSERT (INTO ... SELECT ...) |