Re: Using a single standalone-backend run in initdb (was Re: Bootstrap DATA is a pita) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Using a single standalone-backend run in initdb (was Re: Bootstrap DATA is a pita)
Date
Msg-id 23778.1449967936@sss.pgh.pa.us
Whole thread Raw
In response to Re: Using a single standalone-backend run in initdb (was Re: Bootstrap DATA is a pita)  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> That's cool too. Besides processing the .bki files, and there largely
> reg*_in, the many restarts are the most expensive parts of initdb.

BTW, in case anyone is doubting it, I did a little bit of "perf" tracing
and confirmed Andres' comment here: more than 50% of the runtime of the
bootstrap phase is eaten by the pg_proc seqscans performed by regprocin.
There's nothing else amounting to more than a few percent, so basically
nothing else in bootstrap is worth optimizing before we fix that.
        regards, tom lane



pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: [sqlsmith] Failed to generate plan on lateral subqueries
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] PostGIS Doc Urls