Re: Performing partition pruning using row value

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: "kato-sho(at)fujitsu(dot)com" <kato-sho(at)fujitsu(dot)com>, 'Amit Langote' <amitlangote09(at)gmail(dot)com>
Cc: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Performing partition pruning using row value
Date: 2020-07-08 06:19:34
Message-ID: 7973d37d-bd98-034b-21be-daaa71456191@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020/07/08 13:25, kato-sho(at)fujitsu(dot)com wrote:
> Amit-san
>
> On Wednesday, July 8, 2020 11:53 AM, Amit Langote <amitlangote09(at)gmail(dot)com>:
>> I think the only reason that this is not supported is that I hadn't tested such a
>> query when developing partition pruning, nor did anyone else suggest doing
>> so. :)

Seems we can do partition pruning even in Kato-san's case by dong

create type hoge as (c1 int, c2 int);
create table a( c1 int, c2 int, c3 varchar) partition by range(((c1, c2)::hoge));
create table a1 partition of a for values from((0, 0)) to ((100, 100));
create table a2 partition of a for values from((100, 100)) to ((200, 200));
explain select * from a where (c1, c2)::hoge < (99, 99)::hoge;

I'm not sure if this method is officially supported or not, though...

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2020-07-08 06:22:36 Re: Modifying data type of slot_keep_segs from XLogRecPtr to XLogSegNo
Previous Message Thomas Munro 2020-07-08 06:12:51 Re: Collation versioning