PostgreSQL 10 changes in exclusion constraints - did something change?

From: "Regina Obe" <lr(at)pcorp(dot)us>
To: "'PostgreSQL-development'" <pgsql-hackers(at)postgresql(dot)org>
Subject: PostgreSQL 10 changes in exclusion constraints - did something change?
Date: 2017-05-25 20:47:30
Message-ID: 000901d2d598$211d2870$63577950$@pcorp.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Did something change with how exclusion constraints are handled? I'm trying
to troubleshoot a regression we are having with PostGIS raster support.

As best I can guess, it's because exclusion constraints that used to work in
past versions are failing in PostgreSQL 10 with an error something like
this:

ERROR: conflicting key value violates exclusion constraint
"enforce_spatially_unique_test_raster_columns_rast"
ERROR: new row for relation "test_raster_columns" violates check constraint
"enforce_coverage_tile_rast"

Unfortunately I don't know how long this has been an issue since we had an
earlier test failing preventing the raster ones from being tested.

Thanks,
Regina

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2017-05-25 21:06:45 Re: pg_dump ignoring information_schema tables which used in Create Publication.
Previous Message Jeevan Ladhe 2017-05-25 19:12:14 fix side-effect in get_qual_for_list()