diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2016-04-20 23:48:13 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2016-04-20 23:48:13 -0400 |
| commit | 4c1c9f80b769120f2e809aa6447383c95c7705cf (patch) | |
| tree | 9f058b5aa2c2b6b5b0a54f864a00d789526e9028 /src/backend/access/gist/giststrat.c | |
| parent | f719cd9bfbcf98ce9423b5c01184cf3bc627bbd7 (diff) | |
| download | postgresql-4c1c9f80b769120f2e809aa6447383c95c7705cf.tar.gz postgresql-4c1c9f80b769120f2e809aa6447383c95c7705cf.zip | |
Honor PGCTLTIMEOUT environment variable for pg_regress' startup wait.
In commit 2ffa86962077c588 we made pg_ctl recognize an environment variable
PGCTLTIMEOUT to set the default timeout for starting and stopping the
postmaster. However, pg_regress uses pg_ctl only for the "stop" end of
that; it has bespoke code for starting the postmaster, and that code has
historically had a hard-wired 60-second timeout. Further buildfarm
experience says it'd be a good idea if that timeout were also controlled
by PGCTLTIMEOUT, so let's make it so. Like the previous patch, back-patch
to all active branches.
Discussion: <13969.1461191936@sss.pgh.pa.us>
Diffstat (limited to 'src/backend/access/gist/giststrat.c')
0 files changed, 0 insertions, 0 deletions