diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-04-14 17:51:25 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-04-14 17:51:25 -0400 |
| commit | 85a0781334a204c15c9c6ea9d3e6c75334c2beb6 (patch) | |
| tree | 165967f8a4ee544ef6e0fb371495287d1c2fbe8e /src/backend/executor | |
| parent | 2040bb4a0b50ef0434a1a723f00d040ab4f1c06f (diff) | |
| download | postgresql-85a0781334a204c15c9c6ea9d3e6c75334c2beb6.tar.gz postgresql-85a0781334a204c15c9c6ea9d3e6c75334c2beb6.zip | |
Use one transaction while reading postgres.bki, not one per line.
AFAICT, the only actual benefit of closing a bootstrap transaction
is to reclaim transient memory. We can do that a lot more cheaply
by just doing a MemoryContextReset on a suitable context. This
gets the runtime of the "bootstrap" phase of initdb down to the
point where, at least by eyeball, it's quite negligible compared
to the rest of the phases. Per discussion with Andres Freund.
Discussion: https://postgr.es/m/9244.1492106743@sss.pgh.pa.us
Diffstat (limited to 'src/backend/executor')
0 files changed, 0 insertions, 0 deletions