From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | jian he <jian(dot)universality(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PostgreSQL 18 GA press release draft |
Date: | 2025-09-12 01:51:31 |
Message-ID: | 1bad351b-317f-4240-a697-b9e56ae4a72a@postgresql.org |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 9/10/25 12:29 AM, jian he wrote:
> 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?
I like the suggestion and made the swap. Thanks!
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan S. Katz | 2025-09-12 01:53:29 | Re: PostgreSQL 18 GA press release draft |
Previous Message | Jonathan S. Katz | 2025-09-12 01:49:09 | Re: PostgreSQL 18 GA press release draft |