Re: PostgreSQL 18 GA press release draft - Mailing list pgsql-hackers

From jian he
Subject Re: PostgreSQL 18 GA press release draft
Date
Msg-id CACJufxEBvnhu8ws5sp6Nm7b2qzMJyxkQP+PemxqiopGYVVhjpA@mail.gmail.com
Whole thread Raw
In response to PostgreSQL 18 GA press release draft  ("Jonathan S. Katz" <jkatz@postgresql.org>)
List pgsql-hackers
On Wed, Sep 10, 2025 at 11:13 AM Jonathan S. Katz <jkatz@postgresql.org> wrote:
>
> Hi,
>
> Please review for the press release for the following:
>
> * Correctness and accuracy of what's described - we want to be
> technically correct, but we also need to explain why something matters
> to our users.

PostgreSQL 18 adds [temporal
constraints](https://www.postgresql.org/docs/18/release-18.html#RELEASE-18-CONSTRAINTS)
-- constraints over ranges -- for both `PRIMARY KEY` and `UNIQUE`
constraints using the `WITHOUT OVERLAPS` clause, and on `FOREIGN KEY`
constraints using the `PERIOD` clause.

this link (https://www.postgresql.org/docs/18/release-18.html#RELEASE-18-CONSTRAINTS)
seems not that appropriate, since it does not explain WITHOUT OVERLAPS,
link (https://www.postgresql.org/docs/devel/sql-createtable.html#SQL-CREATETABLE-PARMS-UNIQUE)
would be more appropriate?



pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Query Performance Degradation Due to Partition Scan Order – PostgreSQL v17.6
Next
From: shveta malik
Date:
Subject: Re: Improve pg_sync_replication_slots() to wait for primary to advance