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

From: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
To: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: Clarify use of temporary tables within partition trees
Date: 2018-07-03 06:49:44
Message-ID: b7cc212d-8455-c548-5a71-3cbf6133abd6@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Just realized something...

On 2018/07/03 15:29, Amit Langote wrote:
> Sorry for jumping in late here. I have a comment on the patch.
>
> + /* if there are no partitions then treat this as non-inheritance case. */
> + if (partdesc->nparts == 0)
> + {
> + parentrte->inh = false;
> + return;
> + }
> +
>
> Why is this not near the beginning of expand_partitioned_rtentry()?

This one still stands I think.

> Also, ISTM, this code would be unreachable because
> expand_inherited_rtentry would not call here if the above if statement is
> true, no?

I forgot that expand_partitioned_rtentry() will recursively call itself if
a partition is itself a partitioned table, in which case the above code helps.

Thanks,
Amit

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2018-07-03 07:05:51 Re: pgsql: Clarify use of temporary tables within partition trees
Previous Message Michael Paquier 2018-07-03 06:44:52 Re: pgsql: Clarify use of temporary tables within partition trees

Browse pgsql-hackers by date

  From Date Subject
Next Message Konstantin Knizhnik 2018-07-03 07:03:07 Unusable index
Previous Message Michael Paquier 2018-07-03 06:44:52 Re: pgsql: Clarify use of temporary tables within partition trees