From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
Cc: | Rafia Sabih <rafia(dot)sabih(at)enterprisedb(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Partition-wise join for join between (declaratively) partitioned tables |
Date: | 2017-08-03 01:31:56 |
Message-ID: | CA+TgmobeRUTu4osXA_UA4AORho83WxAvFG8n1NQcoFuujbeh7A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 31, 2017 at 9:07 AM, Ashutosh Bapat
<ashutosh(dot)bapat(at)enterprisedb(dot)com> wrote:
> Forgot the patch set. Here it is.
The commit message for 0005 isn't really accurate given that it
follows 0004. I think you could just flatten 0005 and 0006 into one
patch.
Reviewing those together:
- Existing code does partdesc = RelationGetPartitionDesc(relation) but
this has got it as part_desc. Seems better to be consistent.
Likewise existing variables for PartitionKey are key or partkey, not
part_key.
- get_relation_partition_info has a useless trailing return.
- Instead of adding nparts, boundinfo, and part_oids to RelOptInfo,
how about just adding partdesc? Seems cleaner.
- pkexprs seems like a potentially confusing name, since PK is widely
used to mean "primary key" but here you mean "partition key". Maybe
partkeyexprs.
- build_simple_rel's matching algorithm is O(n^2). We may have talked
about this problem before...
- This patch introduces some bits that are not yet used, like
nullable_pkexprs, or even the code to set the partition scheme for
joinrels. I think perhaps some of that logic should be moved from
0008 to here - e.g. the initial portion of
build_joinrel_partition_info.
There may be more, but I've run out of energy for tonight.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-08-03 01:33:32 | Re: Why does logical replication launcher exit with exit code 1? |
Previous Message | Masahiko Sawada | 2017-08-03 00:59:50 | Re: BUG #14758: Segfault with logical replication on a function index |