Re: [HACKERS] fix empty array expression in get_qual_for_list() - Mailing list pgsql-hackers

From Jeevan Ladhe
Subject Re: [HACKERS] fix empty array expression in get_qual_for_list()
Date
Msg-id CAOgcT0NPQeOP38sBaztjVfZTV_cbAJYdAXgH=WkssKQXWoEM+Q@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] fix empty array expression in get_qual_for_list()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Jun 26, 2017 at 8:14 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Jeevan Ladhe <jeevan.ladhe@enterprisedb.com> writes:
> In case of list partitioned table:
> 1. If there is a partition accepting only null values and nothing else, then
> currently the partition constraints for such a partition are constructed as
> "((a IS NULL) OR (a = ANY (ARRAY[]::integer[])))".
> I think there it is better to avoid constructing an empty array to avoid
> executing ANY expression.

Looks like a good idea, pushed with trivial stylistic adjustments.
 
Thanks Tom for taking care of this.


Regards,
Jeevan Ladhe

pgsql-hackers by date:

Previous
From: nb
Date:
Subject: [HACKERS] pg_basebackup fails on Windows when using tablespace mapping
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Another reason why the recovery tests take a long time