pgsql: In initdb's post-bootstrap phase, drop temp tables explicitly.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: In initdb's post-bootstrap phase, drop temp tables explicitly.
Date: 2016-01-06 17:25:38
Message-ID: E1aGrq6-0007Vd-R6@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

In initdb's post-bootstrap phase, drop temp tables explicitly.

Although these temp tables will get removed from template1 at the end of
the standalone-backend run, that's too late to keep them from getting
copied into the template0 and postgres databases, now that we use only a
single backend run for the whole sequence. While no real harm is done
by the extra copies (since they'd be deleted on first use of the temp
schema), it's still unsightly, and it would mean some wasted cycles for
every database creation for the life of the installation.

Oversight in commit c4a8812cf64b1426. Noticed by Amit Langote.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/dad08994b25b8cd2caa83b2e856fcc940d5e515c

Modified Files
--------------
src/bin/initdb/initdb.c | 13 +++++++++++++
1 file changed, 13 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2016-01-07 15:01:40 pgsql: Windows: Make pg_ctl reliably detect service status
Previous Message Tom Lane 2016-01-06 16:07:08 pgsql: Comment typo fix.