Re: BUG #15222: pg_isready fails connection after previous pg_isready claims success

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: jwatte(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15222: pg_isready fails connection after previous pg_isready claims success
Date: 2018-05-31 16:51:01
Message-ID: 4523.1527785461@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?utf-8?q?PG_Bug_reporting_form?= <noreply(at)postgresql(dot)org> writes:
> When starting up an instance of the postgres Docker container, I'm seeing
> postgres reject a new connection after already having accepted previous
> connections and pg_isready reporting it's ready.

Hmm, does anything show up in the postmaster log when this happens?
(It might be worth turning on log_connections to help ensure there's
some log trace.)

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jon Watte 2018-05-31 21:06:49 Re: BUG #15222: pg_isready fails connection after previous pg_isready claims success
Previous Message PG Bug reporting form 2018-05-31 16:39:01 BUG #15222: pg_isready fails connection after previous pg_isready claims success