Horton

Re: [HACKERS] Cutting initdb's runtime (Perl question embedded)

Andres Freund <andres@anarazel.de>

View thread View on postgr.es
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>, John Naylor <jcnaylor@gmail.com>, Andreas Karlsson <andreas@proxel.se>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2018-05-10T17:40:58Z
Lists: pgsql-hackers 
Hi,

On 2018-05-10 12:18:19 -0400, Tom Lane wrote:
> Next question is what to do with this.  Do we want to sit on it till
> v12, or sneak it in now?

Is there a decent argument for sneaking it in? I don't really have an
opinion. I don't think it'd really be arguable that this'll make testing
meaningfully faster. OTOH, it's fresh in your mind (which can be said
about a lot of patches obviously).

Greetings,

Andres Freund

Commits

  1. Attempt to identify system timezone by reading /etc/localtime symlink.

  2. Make sure to run one initdb TAP test with no TZ set

  3. Use one transaction while reading postgres.bki, not one per line.

  4. Move bootstrap-time lookup of regproc OIDs into genbki.pl.