Re: Problem with default partition pruning - Mailing list pgsql-hackers

From Kyotaro HORIGUCHI
Subject Re: Problem with default partition pruning
Date
Msg-id 20190319.114041.61514593.horiguchi.kyotaro@lab.ntt.co.jp
Whole thread Raw
In response to Re: Problem with default partition pruning  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
List pgsql-hackers
Hello.

At Fri, 15 Mar 2019 17:30:07 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp> wrote in
<20190315.173007.147577546.horiguchi.kyotaro@lab.ntt.co.jp>
> The patch relies on the fact(?) that the lowest index is always
> -1 in range partition and uses it as pseudo default
> partition. I'm not sure it is really the fact and anyway it
> donsn't seem the right thing to do. Could you explain how it
> works, not what you did in this patch?

I understood how it works but still uneasy that only list
partitioning requires scan_default. Anyway please ignore this.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-hackers by date:

Previous
From: Eric Hanson
Date:
Subject: extensions are hitting the ceiling
Next
From: "Yamaji, Ryo"
Date:
Subject: RE: [HACKERS] Cached plans and statement generalization