Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1czPuD-0000uC-7T for pgsql-hackers@arkaria.postgresql.org; Sat, 15 Apr 2017 15:46:33 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1czPuC-0005Et-Qp for pgsql-hackers@arkaria.postgresql.org; Sat, 15 Apr 2017 15:46:32 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1czPsh-0002V0-0d for pgsql-hackers@postgresql.org; Sat, 15 Apr 2017 15:44:59 +0000 Received: from mail-qk0-x229.google.com ([2607:f8b0:400d:c09::229]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1czPsZ-0006Fq-TV for pgsql-hackers@postgresql.org; Sat, 15 Apr 2017 15:44:57 +0000 Received: by mail-qk0-x229.google.com with SMTP id h67so83052835qke.0 for ; Sat, 15 Apr 2017 08:44:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=Y7DC4qZILtSZzaLWCgVtr+8adbvjayq30zrfYruH0A8=; b=rcsNnr84YNLSI5t6uwugymLaks0Ow66mac9ESupNStJ4ywfxKmQ2Rs0H47cfRmH9E/ ASERqyCZGkiuMT63hePZGYjs9CU5+hXpU3oihCWWLXtktQmRgAzNNkVTjY5MYjTt8h5s jLKs4wRBGopAX3Xgvvsrka1xmN0KB4R7lstjDJeBFCq5md/dcNfXhJ/KRrUtotq9Z7vk 9vMg9jg2MHGFOaao/pVzKdqXXdE1WoHJQH2Y5Zv02Hh5F+pWN7mhk74ZXy825s14pIt5 5TjNNVYFOroDGsLmx50b9eHArCdB0umWZ3sJCINcq4s06cqyLxAOF703rlZN6Md4oYat PMqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=Y7DC4qZILtSZzaLWCgVtr+8adbvjayq30zrfYruH0A8=; b=k1yCoUVo6FzNFRrTSWUZhbQN9gcwXvwfmpnqbIuW+qfpD103FkOoAx3yVOYXr038Oo ZmHH/XJyM0GwgVzQVPKGNjmcEt+tGGJxZuQiaKpCa++mTioybiEGa9y+2R6/Dl75ha/b EYfzs6UIdhkhKaRhIPSVMInHzIyek0b7Mk3Y1AtjL4nTbXUhUidyAYah2B1UJHE4zAn7 MELKGS+1GqX/E4ixIh3/B7jz8p7i22vF99XRKUWCKXhfh04BMvdhi4W3CTBgk6TGEmiy PzAKJlwBXcNsbgw1fbTOwZTjxRe2t5zQLOfERGUasR+e/JfOsnzhYP2jn51yzG41NJCq 9paw== X-Gm-Message-State: AN3rC/6QIJ7sJ10OA0GZ+ixeDXBEhkQBNAAL9vki6OGhWpBRzNhU9SZP SXeGs40xFyJkEPCghOI= X-Received: by 10.55.103.199 with SMTP id b190mr2326808qkc.90.1492271090255; Sat, 15 Apr 2017 08:44:50 -0700 (PDT) Received: from alvin.alvh.no-ip.org ([190.217.208.245]) by smtp.gmail.com with ESMTPSA id v63sm3372232qkc.5.2017.04.15.08.44.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 15 Apr 2017 08:44:49 -0700 (PDT) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id 2AFFC738; Sat, 15 Apr 2017 12:44:40 -0300 (-03) Date: Sat, 15 Apr 2017 12:44:40 -0300 From: Alvaro Herrera To: Andrew Dunstan Cc: Tom Lane , Andreas Karlsson , Andres Freund , pgsql-hackers@postgresql.org Subject: Re: Cutting initdb's runtime (Perl question embedded) Message-ID: <20170415154440.3eg3dltxs5zybmv2@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20170306-137-4415bd-dirty (1.8.0) X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Andrew Dunstan wrote: > Alternatively, we could have an initdb TAP test that explicitly removed > the environment setting so we'd get coverage of select_default_timezone, > and have the buildfarm set TZ to something if it's not already set. What about having an initdb option that runs select_default_timezone only and reports the result, so that it can be used in the buildfarm script to set TZ in all the regular initdb calls? -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers