Re: Invalid indexes should not consume update overhead

From: Jan Wieck <jan(at)wi3ck(dot)info>
To: "Rader, David" <davidr(at)openscg(dot)com>
Cc: Peter Geoghegan <pg(at)heroku(dot)com>, Tomasz Ostrowski <tometzky+pg(at)ato(dot)waw(dot)pl>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>, Greg Stark <stark(at)mit(dot)edu>
Subject: Re: Invalid indexes should not consume update overhead
Date: 2016-07-17 21:19:52
Message-ID: CAGBW59cMWhLcCqzkR_eubhJkKS1MyMWh5GBPNkxn=n7FtAgkpQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sun, Jul 17, 2016 at 5:06 PM, Rader, David <davidr(at)openscg(dot)com> wrote:

>
>
> Of course then you have to be sure that your data is right when you bulk
> load since the engine is not enforcing it.
>
>
Correct. But that won't be different from a NOT VALID constraint (see
https://www.postgresql.org/docs/9.5/static/sql-altertable.html)

Jan

--
Jan Wieck
Senior Postgres Architect
http://pgblog.wi3ck.info

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Rader, David 2016-07-17 21:20:07 Re: Invalid indexes should not consume update overhead
Previous Message Jan Wieck 2016-07-17 21:12:27 Re: Invalid indexes should not consume update overhead