Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

backend

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    In commit 2ffa8696 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>
    cbabb70f
    History
    Name Last commit Last update
    ..