On 9/9/25 11:13 PM, Jonathan S. Katz wrote:
Hi,
Attached is a draft of the PostgreSQL 18 GA press release. A few
comments before the ask for reviewing:
* I still need to write up the theme and the quote, which I'll provide
tomorrow after hearing the first round of feedback
* The release is a
On Wed, Sep 10, 2025 at 10:13 AM Jonathan S. Katz wrote:
> PostgreSQL 18 also supports using x86 AVX-512 instructions for CRC32
> calculations, which are used in page checksums and are also available in the
> new
> [`crc32`](https://www.postgresql.org/docs/18/functions-binarystring.html#FUNCTI
On 9/12/25 11:46 AM, Jonathan S. Katz wrote:
As per above, I'll need remaining feedback no later than 2025-09-14 0:00
UTC - after this, it's frozen for the translation process to begin.
Thank everyone for your feedback. I've attached the copy of the release
announcement that will be translate
On 9/12/25 3:24 PM, Álvaro Herrera wrote:
Hello,
Thanks for putting this together! It's quite the monster. I read
through and found the following points worth mentioning:
Thank you!
I think almost all of the non-stock section titles Are Lacking Case
Title.
Putting this is as an example o
On Sun, 2025-09-14 at 09:41 -0400, Jonathan S. Katz wrote:
> I went with breaking this up into two sentences:
>
> This release adds the
> [`PG_UNICODE_FAST`](
> https://www.postgresql.org/docs/18/collation.html#COLLATION-MANAGING-
> STANDARD),
> which provides full Unicode semantics for case tra
On 9/12/25 1:11 PM, Jeff Davis wrote:
On Tue, 2025-09-09 at 23:13 -0400, Jonathan S. Katz wrote:
Hi,
Attached is a draft of the PostgreSQL 18 GA press release. A few
comments before the ask for reviewing:
"This release adds the [`PG_UNICODE_FAST`], which accelerates lookups
using the `upper`
On 9/12/25 2:18 PM, Masahiko Sawada wrote:
I found a typo;
s/gen_rand_uuid()/gen_random_uuid()/
Good catch - thanks!
Jonathan
OpenPGP_signature.asc
Description: OpenPGP digital signature
On Fri, 2025-09-12 at 13:21 -0500, Nico Williams wrote:
> On Fri, Sep 12, 2025 at 10:11:59AM -0700, Jeff Davis wrote:
> > The name PG_UNICODE_FAST is meant to convey that it provides full
> > unicode semantics for case mapping and pattern matching, while also
> > being fast because it uses memcmp f
On Fri, 2025-09-12 at 15:48 -0500, Nico Williams wrote:
> I meant form-insensitive, as in comparing equivalent strings where
> one
> might be using decomposed sequences and another pre-conposed
> sequences
> (and either might be normalized or not at all).
Use NORMALIZE(a) = NORMALIZE(b).
This is
On Fri, Sep 12, 2025 at 12:13:23PM -0700, Jeff Davis wrote:
> On Fri, 2025-09-12 at 13:21 -0500, Nico Williams wrote:
> > How does one do form-insensitive comparisons?
>
> If you mean case insensitive matching, you can do:
I meant form-insensitive, as in comparing equivalent strings where one
mig
Hello,
Thanks for putting this together! It's quite the monster. I read
through and found the following points worth mentioning:
I think almost all of the non-stock section titles Are Lacking Case
Title.
> The new
> [`io_method`](https://www.postgresql.org/docs/18/runtime-config-resource.html
On Fri, Sep 12, 2025 at 10:11:59AM -0700, Jeff Davis wrote:
> The name PG_UNICODE_FAST is meant to convey that it provides full
> unicode semantics for case mapping and pattern matching, while also
> being fast because it uses memcmp for comparisons. While the name
> PG_C_UTF8 is meant to convey th
On Fri, Sep 12, 2025 at 8:46 AM Jonathan S. Katz wrote:
>
> On 9/9/25 11:13 PM, Jonathan S. Katz wrote:
> > Hi,
> >
> > Attached is a draft of the PostgreSQL 18 GA press release. A few
> > comments before the ask for reviewing:
> >
> > * I still need to write up the theme and the quote, which I'll
On Tue, 2025-09-09 at 23:13 -0400, Jonathan S. Katz wrote:
> Hi,
>
> Attached is a draft of the PostgreSQL 18 GA press release. A few
> comments before the ask for reviewing:
"This release adds the [`PG_UNICODE_FAST`], which accelerates lookups
using the `upper` and `lower` string comparison fun
On Wed, Sep 10, 2025 at 5:14 AM Jonathan S. Katz wrote:
>
> Hi,
>
> Attached is a draft of the PostgreSQL 18 GA press release. A few
> comments before the ask for reviewing:
>
Hi Jonathan,
> Finally, PostgreSQL 18 introduces support for [NUMA
> awareness](https://www.postgresql.org/docs/18/inst
On Wed, Sep 10, 2025 at 6:13 AM Jonathan S. Katz
wrote:
> Hi,
>
> Attached is a draft of the PostgreSQL 18 GA press release. A few
> comments before the ask for reviewing:
>
> * I still need to write up the theme and the quote, which I'll provide
> tomorrow after hearing the first round of feedba
On Thu, Sep 11, 2025 at 10:21 PM Jonathan S. Katz wrote:
> Thanks for the detailed explanation, I'm proposing:
>
> "It can also optimize queries that use `OR` conditions in a `WHERE` to
> use an index, leading to significantly faster execution."
>
> since the mechanism of the transformation is les
On 9/10/25 3:59 PM, Peter Geoghegan wrote:
"It can also automatically transform queries with `OR` constructs in
their `WHERE` clause into a logically equivalent IN() representation
that can be pushed down to index scan nodes, leading to significantly
faster execution".
Thanks for the detailed
On 9/10/25 9:52 AM, John Naylor wrote:
On Wed, Sep 10, 2025 at 10:13 AM Jonathan S. Katz wrote:
PostgreSQL 18 also supports using x86 AVX-512 instructions for CRC32
calculations, which are used in page checksums and are also available in the
new
[`crc32`](https://www.postgresql.org/docs/18/
On 9/10/25 2:58 AM, Jakub Wartak wrote:
and just leave it as
"Finally, PostgreSQL 18 adds basic [NUMA observability]" ?
Rationale: for every other software that I saw NUMA awareness
reference was always linked to gaining performance , but just linking
against libnuma is not giving us this.
Hm
On 9/10/25 12:29 AM, jian he wrote:
On Wed, Sep 10, 2025 at 11:13 AM Jonathan S. Katz 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
On 9/9/25 11:38 PM, Peter Smith wrote:
FWIW, here are a couple of AI-detected issues.
This typo:
"with contains installers" should be "which contains installers"
Thanks!
This potential mismatch:
"Built on over 35 years of engineering" is inconsistent with the
earlier "nearly 30 years" statem
On Tue, Sep 9, 2025 at 11:13 PM Jonathan S. Katz wrote:
> Attached is a draft of the PostgreSQL 18 GA press release.
I have some feedback on this sentence:
"It can also automatically optimize queries using `OR` or `IN (VALUES
...)` in `WHERE` clauses for faster execution".
This is factually cor
On Wed, Sep 10, 2025 at 11:13 AM Jonathan S. Katz 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 add
Hi,
Attached is a draft of the PostgreSQL 18 GA press release. A few
comments before the ask for reviewing:
* I still need to write up the theme and the quote, which I'll provide
tomorrow after hearing the first round of feedback
* The release is a bit long - this is due in part to what I thi
FWIW, here are a couple of AI-detected issues.
This typo:
"with contains installers" should be "which contains installers"
This potential mismatch:
"Built on over 35 years of engineering" is inconsistent with the
earlier "nearly 30 years" statement?
==
Kind Regards,
Peter Smith.
Fujitsu Aust
26 matches
Mail list logo
