Horton

Re: pgsql: Clarify use of temporary tables within partition trees

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: David Rowley <david.rowley@2ndquadrant.com>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Robert Haas <robertmhaas@gmail.com>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, pgsql-committers <pgsql-committers@postgresql.org>
Date: 2018-07-04T01:48:52Z
Lists: pgsql-hackers 
On Tue, Jul 03, 2018 at 08:31:27PM +0900, Michael Paquier wrote:
> I am not sure if it is much interesting to keep around this table set
> for pg_upgrade, so I would drop it.  Except for that, the result looks
> fine.  I'll double-check and wrap it tomorrow on HEAD and REL_11_STABLE.
> The optimizations mentioned sound interesting, though I would recommend
> to not risk the stability of v11 at this point, so let's keep them for
> v12~.

So at the end I have dropped the table from the test, and pushed the
patch to HEAD and REL_11_STABLE.  Thanks David for the patch, and others
for the reviews.
--
Michael

Commits

  1. Remove dead code for temporary relations in partition planning

  2. Clarify use of temporary tables within partition trees

  3. Expand partitioned table RTEs level by level, without flattening.