jw1u1

We do face archive files with invalid s3 checksums and zero byte size with pgbackrest 2.40 and suspect multi-part. It would be great to be able disable it.

concourse is version: v7.8.2 now. Postgres is stillversion 11. Still tons of foreign keys with ON DELETE CASCADE. This isn't how a database schema should look alike, regardless of the...

> Please see the documentation for what `infinite_time_partitions` is for. It doesn't have anything to do with the infinity value. It's to tell pg_partman to keep making time-based partitions infinitely...

> I'm honestly not sure if PostgreSQL itself can support a partition boundary of infinity. Would have to test. postgres=# insert into public.foo_bar (event_cause, event_ts) VALUES ('bar', 'infinity'); INSERT 0...

> Yes, the value itself is a supported thing in PostgreSQL. But does that table have any constraint boundaries on the `event_ts` column? Interesting: Partition constraint: ((event_cause IS NOT NULL)...

> But just to be sure, infinite values are considered valid in your case and this wasn't errant data that someone put in? Yes, they are valid. We could work...

This is where people start to use 9999-12-31 as a workaround...

Hi Keith, we have to set constraint_valid to false to prevent locking issues. I cannot confirm if the maintenance run or the reapply created the constraints. Thanks, Jens

Same here with 2.15.3 when upgrading from Pg 13 to 16 with table chunk_constraint: New cluster database "foo" is not empty: found relation "_timescaledb_catalog.chunk_constraint" There is only 1 Database in...

We have infinite_time_partition set to true and after restarting postgres it worked as expected, so i guess it has nothing to do with no new data.