| From: | jian he <jian(dot)universality(at)gmail(dot)com> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 18 GA press release draft |
| Date: | 2025-09-10 04:29:01 |
| Message-ID: | CACJufxEBvnhu8ws5sp6Nm7b2qzMJyxkQP+PemxqiopGYVVhjpA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 10, 2025 at 11:13 AM Jonathan S. Katz <jkatz(at)postgresql(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2025-09-10 04:45:31 | Re: Improve pg_sync_replication_slots() to wait for primary to advance |
| Previous Message | Ashutosh Bapat | 2025-09-10 04:26:18 | Re: Query Performance Degradation Due to Partition Scan Order – PostgreSQL v17.6 |