On Mon, Jan 5, 2026 at 1:39 PM John Naylor <[email protected]> wrote: > > On Fri, Dec 19, 2025 at 11:00 PM Heikki Linnakangas <[email protected]> wrote: > > > > On 19/12/2025 17:14, Fujii Masao wrote:
> > > This change made me wonder whether we should also update the > > > pg_hba.conf examples > > > in high-availability.sgml and logical-replication.sgml. I've attached > > > a patch for that. Thoughts? > > Sorry, I neglected to look around for similar places to update. I > don't see any other such places, so I will commit this and backpatch > to PG18 as well. I pushed your patch, thanks! > > Let's update this example in createuser.sgml too while we're at it: > > > > <computeroutput>CREATE ROLE joe PASSWORD > > > 'md5b5f5ba1a423792b526f799ae4eb3d59e' SUPERUSER CREATEDB CREATEROLE > > > INHERIT LOGIN;</computeroutput> > This will need to be backpatched to PG14. Unlike the md5 case, the > encrypted password will not be reproducible. Since the above omission > hasn't been noticed, I don't suppose we need to call out this fact? I pushed a fix for this, including missing tokens for earlier branches (and decided not to mention random salt for the example). -- John Naylor Amazon Web Services
