On Wed, May 7, 2025 at 02:52:27PM -0700, Jacob Champion wrote:
> On Wed, May 7, 2025 at 2:45 PM Jonathan S. Katz wrote:
> > I did a double take on the current sentence, and revised it to:
> >
> > ==
> > PostgreSQL 18 introduces `oauth` authentication, which lets users
> > authenticate using OAuth
On Wed, May 7, 2025 at 2:45 PM Jonathan S. Katz wrote:
> I did a double take on the current sentence, and revised it to:
>
> ==
> PostgreSQL 18 introduces `oauth` authentication, which lets users
> authenticate using OAuth 2.0 mechanisms supported through PostgreSQL
> extensions.
> ==
>
> I don't
On 5/7/25 5:16 PM, Jacob Champion wrote:
On Tue, May 6, 2025 at 8:46 PM Jonathan S. Katz wrote:
Here's the next update
Thanks!
PostgreSQL 18 introduces `oauth` authentication, which people can create
extensions that support OAuth 2.0 based authentication mechanisms that
PostgreSQL can aut
On 5/7/25 4:54 PM, Bruce Momjian wrote:
On Tue, May 6, 2025 at 11:24:44PM -0400, Jonathan Katz wrote:
On 5/6/25 11:17 AM, Nathan Bossart wrote:
IMHO we should emphasize that MD5 password support will be removed in a
future release and that users should migrate to something else soon. I'm
ima
On 5/7/25 5:38 AM, Matthias van de Meent wrote:
On Mon, 5 May 2025 at 21:07, Jonathan S. Katz wrote:
Hi,
Attached is a draft of the PostgreSQL 18 Beta 1 release announcement.
The goal of this announcement is to introduce the new capabilities
planned for PostgreSQL 18 and give users an idea of
On 5/7/25 5:18 AM, Jelte Fennema-Nio wrote:
On Mon, 5 May 2025 at 21:07, Jonathan S. Katz wrote:
Attached is a draft of the PostgreSQL 18 Beta 1 release announcement.
It might make sense to add a small sentence like "this release
introduces version 3.2 of the wire protocol, but libpq still us
On Tue, May 6, 2025 at 8:46 PM Jonathan S. Katz wrote:
> Here's the next update
Thanks!
> PostgreSQL 18 introduces `oauth` authentication, which people can create
> extensions that support OAuth 2.0 based authentication mechanisms that
> PostgreSQL can authenticate with.
Suggested alternative
On Tue, May 6, 2025 at 11:24:44PM -0400, Jonathan Katz wrote:
> On 5/6/25 11:17 AM, Nathan Bossart wrote:
>
> > IMHO we should emphasize that MD5 password support will be removed in a
> > future release and that users should migrate to something else soon. I'm
> > imagining it'll still be at lea
On Tue, May 06, 2025 at 11:24:44PM -0400, Jonathan S. Katz wrote:
> I took most of these changes. I don't think we should add the MD5 "will be
> removed in a future release" in the beta announcement, as that could lead to
> confusion (e.g. it's removed in beta 2!). I'm fine with adding that in the
On Mon, 5 May 2025 at 21:07, Jonathan S. Katz wrote:
>
> Hi,
>
> Attached is a draft of the PostgreSQL 18 Beta 1 release announcement.
> The goal of this announcement is to introduce the new capabilities
> planned for PostgreSQL 18 and give users an idea of areas we'd like to
> see tested.
>
> Ple
On Mon, 5 May 2025 at 21:07, Jonathan S. Katz wrote:
> Attached is a draft of the PostgreSQL 18 Beta 1 release announcement.
It might make sense to add a small sentence like "this release
introduces version 3.2 of the wire protocol, but libpq still uses 3.0
by default. This is the first new proto
On 2025-May-06, Jonathan S. Katz wrote:
> Here's the next update (CCing folks who commented); I added a sentence on
> the new constraints that are available in the developer experience section,
> and the sentence around the behavior towards the bottom. Please let me know
> if you think this suffic
On 5/6/25 9:15 AM, Álvaro Herrera wrote:
On 2025-May-05, Jonathan S. Katz wrote:
### Other Highlights
Starting with PostgreSQL 18, data checksums, which are used to validate the
integrity of stored data, are now enabled by default on new PostgreSQL
clusters. You can choose to disable this be
On 5/6/25 11:55 AM, Andres Freund wrote:
Hi,
On 2025-05-05 15:07:01 -0400, Jonathan S. Katz wrote:
### Performance
PostgreSQL 18 introduces an asynchronous I/O (AIO) subsystem using
`io_uring` on Linux, which, when combined with direct I/O (DIO), lets
PostgreSQL directly interface with storage
On 5/6/25 11:17 AM, Nathan Bossart wrote:
IMHO we should emphasize that MD5 password support will be removed in a
future release and that users should migrate to something else soon. I'm
imagining it'll still be at least a couple of years before I muster up the
courage to actually propose remov
Hi,
On 2025-05-06 16:53:46 -0400, Bruce Momjian wrote:
> On Tue, May 6, 2025 at 11:55:53AM -0400, Andres Freund wrote:
> > On 2025-05-05 15:07:01 -0400, Jonathan S. Katz wrote:
> > > ### Performance
> > >
> > > PostgreSQL 18 introduces an asynchronous I/O (AIO) subsystem using
> > > `io_uring` on
On Tue, May 6, 2025 at 11:55:53AM -0400, Andres Freund wrote:
> Hi,
>
> On 2025-05-05 15:07:01 -0400, Jonathan S. Katz wrote:
> > ### Performance
> >
> > PostgreSQL 18 introduces an asynchronous I/O (AIO) subsystem using
> > `io_uring` on Linux, which, when combined with direct I/O (DIO), lets
>
Hi,
On 2025-05-05 15:07:01 -0400, Jonathan S. Katz wrote:
> ### Performance
>
> PostgreSQL 18 introduces an asynchronous I/O (AIO) subsystem using
> `io_uring` on Linux, which, when combined with direct I/O (DIO), lets
> PostgreSQL directly interface with storage interfaces. This new subsystem
> g
On Mon, May 05, 2025 at 03:07:01PM -0400, Jonathan S. Katz wrote:
> Before PostgreSQL 18, an important step after performing a major version
> upgrade was to run the `ANALYZE` to generate statistics, which is a
> critical component of helping PostgreSQL to select the most efficient
> query plan. Ba
On 2025-May-05, Jonathan S. Katz wrote:
> ### Other Highlights
>
> Starting with PostgreSQL 18, data checksums, which are used to validate the
> integrity of stored data, are now enabled by default on new PostgreSQL
> clusters. You can choose to disable this behavior using the `initdb
> --no-d
Hi,
On Mon, May 05, 2025 at 03:07:01PM -0400, Jonathan S. Katz wrote:
> Hi,
>
> Attached is a draft of the PostgreSQL 18 Beta 1 release announcement.
Thanks for working on it!
One small feedback on this:
"
and now shows per-connection statistics on I/O utilization
"
I think we can add WAL to
On Mon, May 5, 2025 at 3:07 PM Jonathan S. Katz wrote:
>
> Hi,
>
> Attached is a draft of the PostgreSQL 18 Beta 1 release announcement.
> The goal of this announcement is to introduce the new capabilities
> planned for PostgreSQL 18 and give users an idea of areas we'd like to
> see tested.
>
> P
Hi,
Attached is a draft of the PostgreSQL 18 Beta 1 release announcement.
The goal of this announcement is to introduce the new capabilities
planned for PostgreSQL 18 and give users an idea of areas we'd like to
see tested.
Please check for accuracy and if there are glaring omissions (happy
23 matches
Mail list logo
