| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: default range partition and constraint exclusion |
| Date: | 2017-11-27 21:01:07 |
| Message-ID: | CA+Tgmoa84t92mJoNRyAi+n0CWEAg436_tsX3cJRQ4qsSj1cdZw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 27, 2017 at 4:04 AM, Kyotaro HORIGUCHI
<horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> This is the story in my understanding.
Thanks, that's helpful. Sorry I didn't have time yet to study this in
detail myself. If we're routing tuples to a partition for which the
partition constraint is evaluating to null, that's OK, but if we're
routing tuples to a partition for which the partition constraint is
evaluating to false, that's a bug, and the right solution is to
correct either the tuple routing or the partition constraint. In this
case, it looks like the tuple routing is working as expected, so that
would say we ought to fix the constraint.
I am out of time for today but will try to look at this some more tomorrow.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2017-11-27 21:05:06 | Re: [HACKERS] More stats about skipped vacuums |
| Previous Message | Tomas Vondra | 2017-11-27 20:34:52 | simplehash: tb->sizemask = 0 |