I'm relatively unsure where and how to proceed.
Short version:
I dumped a table with an exclude constraint with pg_dump, and loaded it
into another instance of postgres where it promptly failed to create the
constraint. The complaint was... key conflicts with key. IOW,
duplicate data.
Thi
Jeff Davis wrote:
Are you using any floating point values, or floating-point timestamps
(that's a compile-time option)?
I'm using whatever the default compile time options are.
It's worth noting that if I delete the row, and then attempt to insert
a row with the same data on the original data
Tom Lane wrote:
Alex Zepeda writes:
If I try to manually add the constraint on the table I get:
blockface=# alter table bus_positions add constraint "exclude_time_buffer" EXCLUDE USING gist
(vehicle WITH =, buffer_time WITH &&, bbox_dup WITH &&);
NOTICE: ALTER TABLE
Tom Lane wrote:
Alex Zepeda writes:
I'd be happy to provide someone with a copy of the dump...
but it's ~70MB bzip'd.
I'd be willing to take a look ... but if my WAG is right, the insertion
order would be critical information to reproduce the problem. Is it
possible to
Tom Lane wrote:
So these two geometry values do not overlap in the original database,
but they do overlap in the clone, apparently because the output
representation of geometry doesn't result in an exact reconstruction
of the value. Somebody better complain over in the postgis lists.
Thanks f
