Обсуждение: [PATCH] Documentation
Hi
This is my first ever patch to postgresql so please guide me if i'm doing something wrong.
This patch updates some examples in documentation client-auth.sgml from md5 to scram-sha-256
Reference: https://www.postgresql.org/message-id/176595607507.978865.11597773194269211255%40wrigleys.postgresql.org
KR
Mikael Gustavsson, SMHI
Вложения
On 12/18/25 8:31 AM, Mikael Gustavsson wrote: > This is my first ever patch to postgresql so please guide me if i'm > doing something wrong. > > This patch updates some examples in documentation client-auth.sgml from > md5 to scram-sha-256 > Reference: https://www.postgresql.org/message- > id/176595607507.978865.11597773194269211255%40wrigleys.postgresql.org > <https://www.postgresql.org/message- > id/176595607507.978865.11597773194269211255%40wrigleys.postgresql.org> Välkommen! The patch looks good to me and it looks like a useful change. To make sure it is not lost you can add it to the current open commitfest but it is also possible that some committer will just pick up the patch directly. You can add it here: https://commitfest.postgresql.org/ I personally usually use "git format-patch" when submitting to the mailing list but this format works just as well if it is just one simple patch like this and not a series of multiple patches. Thanks for the patch! Andreas
On Thu, 2025-12-18 at 08:51 +0100, Andreas Karlsson wrote: > On 12/18/25 8:31 AM, Mikael Gustavsson wrote: > > This is my first ever patch to postgresql so please guide me if i'm > > doing something wrong. > > > > This patch updates some examples in documentation client-auth.sgml from > > md5 to scram-sha-256 > > Reference: https://www.postgresql.org/message- > > id/176595607507.978865.11597773194269211255%40wrigleys.postgresql.org > > <https://www.postgresql.org/message- > > id/176595607507.978865.11597773194269211255%40wrigleys.postgresql.org> > > The patch looks good to me and it looks like a useful change. +1 Yours, Laurenz Albe
On Thu, Dec 18, 2025 at 2:51 PM Andreas Karlsson <andreas@proxel.se> wrote: > The patch looks good to me and it looks like a useful change. To make > sure it is not lost you can add it to the current open commitfest but it > is also possible that some committer will just pick up the patch directly. I can commit this tomorrow. Deprecating md5 came into v18, so even though this is not a correction, we could backpatch this to v18 for consistency. Anyone want to make a case for or against? -- John Naylor Amazon Web Services