Re: BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username` - Mailing list pgsql-bugs

From Jacob Champion
Subject Re: BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username`
Date
Msg-id CAOYmi+mAWLmb6egMet8LFy_vDC7euHLFHQnFjL36MiFrjvySTg@mail.gmail.com
Whole thread Raw
In response to BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username`  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username`
List pgsql-bugs
On Tue, Jul 29, 2025 at 12:45 PM PG Bug reporting form
<noreply@postgresql.org> wrote:
> /  > pg_isready -U fff
> /tmp:5432 - accepting connections
> /  > pg_isready -U fff -d555
> /tmp:5432 - accepting connections
> ```
>
> (`fff` is not a user and `555` is not a db on my installation)

Hi Samuel, this behavior is explained in the docs [1]:

> It is not necessary to supply correct user name, password, or database name values to obtain the server status;
however,if incorrect values are provided, the server will log a failed connection attempt. 

So it's essentially just a courtesy to whoever's watching your logs.

--Jacob

[1] https://www.postgresql.org/docs/current/app-pg-isready.html#APP-PG-ISREADY-NOTES



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username`
Next
From: Jeff Davis
Date:
Subject: CREATE DATABASE copies datlocale even if datlocprovider differs