Re: no partition pruning when partitioning using array type - Mailing list pgsql-hackers

From Amit Langote
Subject Re: no partition pruning when partitioning using array type
Date
Msg-id 48e5232d-ba7a-1670-984a-0e8d4413323c@lab.ntt.co.jp
Whole thread Raw
In response to Re: no partition pruning when partitioning using array type  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: no partition pruning when partitioning using array type  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 2018/07/11 4:50, Alvaro Herrera wrote:
> On 2018-Jul-10, Tom Lane wrote:
> 
>> And what about those partition bound values?  They are now illegal
>> for the domain, so I would expect a dump/reload to fail, regardless
>> of whether there are any values in the table.
> 
> Hmm, true.

There is a patch to overhaul how partition bound values are parsed:

https://commitfest.postgresql.org/18/1620/

With that patch, the error you reported upthread goes away (that is, one
can successfully create partitions), but the problem that Tom mentioned
above then appears.

What's the solution here then?  Prevent domains as partition key?

Thanks,
Amit



pgsql-hackers by date:

Previous
From: "Yang Jie"
Date:
Subject: Re: user-friendliness improvement of pageinspect
Next
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] SERIALIZABLE with parallel query