| Lists: | pgsql-bugs |
|---|
| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | vonproteus+postgresql(dot)org(at)gmail(dot)com |
| Subject: | BUG #16353: pg_isready timeout is ignored |
| Date: | 2020-04-09 06:00:39 |
| Message-ID: | 16353-9c7912834e84c78e@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 16353
Logged by: vonProteus
Email address: vonproteus+postgresql(dot)org(at)gmail(dot)com
PostgreSQL version: 11.7
Operating system: docker postgres:11-alpine (x64)
Description:
hi
i have problem with pg_isready and time out
it look like it is ignored
this is my setup
$ docker run --name some-postgres -e POSTGRES_PASSWORD=mysecretpassword -p
3333:5432 --rm -d postgres:11-alpine
4765f8dc49374044d551b3cdb0ce5284905ee1c01bf6a81b2cddf30ab6798bc8
$ time docker run --rm postgres:11-alpine pg_isready -t 120 -h
10.110.12.163 -p 3333
10.110.12.163:3333 - accepting connections
real 0m0.781s
user 0m0.000s
sys 0m0.031s
$ docker stop some-postgres
some-postgres
$ time docker run --rm postgres:11-alpine pg_isready -t 120 -h
10.110.12.163 -p 3333
10.110.12.163:3333 - no response
real 0m2.722s
user 0m0.000s
sys 0m0.031s
i would expect that second call would exit after 120s
i run this on windows
| From: | Hamid Akhtar <hamid(dot)akhtar(at)gmail(dot)com> |
|---|---|
| To: | vonproteus+postgresql(dot)org(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16353: pg_isready timeout is ignored |
| Date: | 2020-04-09 07:45:26 |
| Message-ID: | CANugjht_dCJPpqFbDHVYcncgw=tm_p8ka_=0+QWJt08gb+GnLg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-bugs |
For pg_isready attempts to make a connection with the sever. If a
connection is not successful and we didn't receive any error response from
the server, it is a fair assumption to make that server is not running. In
this case, it makes perfect sense to not honour the timeout value and
return immediately.
So, this is actually not a bug but rather an expected behaviour.
On Thu, Apr 9, 2020 at 11:18 AM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 16353
> Logged by: vonProteus
> Email address: vonproteus+postgresql(dot)org(at)gmail(dot)com
> PostgreSQL version: 11.7
> Operating system: docker postgres:11-alpine (x64)
> Description:
>
> hi
> i have problem with pg_isready and time out
> it look like it is ignored
> this is my setup
>
> $ docker run --name some-postgres -e POSTGRES_PASSWORD=mysecretpassword -p
> 3333:5432 --rm -d postgres:11-alpine
> 4765f8dc49374044d551b3cdb0ce5284905ee1c01bf6a81b2cddf30ab6798bc8
>
> $ time docker run --rm postgres:11-alpine pg_isready -t 120 -h
> 10.110.12.163 -p 3333
> 10.110.12.163:3333 - accepting connections
>
> real 0m0.781s
> user 0m0.000s
> sys 0m0.031s
>
> $ docker stop some-postgres
> some-postgres
>
> $ time docker run --rm postgres:11-alpine pg_isready -t 120 -h
> 10.110.12.163 -p 3333
> 10.110.12.163:3333 - no response
>
> real 0m2.722s
> user 0m0.000s
> sys 0m0.031s
>
> i would expect that second call would exit after 120s
> i run this on windows
>
>
--
Highgo Software (Canada/China/Pakistan)
URL : www.highgo.ca
ADDR: 10318 WHALLEY BLVD, Surrey, BC
CELL：+923335449950 EMAIL: mailto:hamid(dot)akhtar(at)highgo(dot)ca
SKYPE: engineeredvirus