Re: fix empty array expression in get_qual_for_list()

From: Jeevan Ladhe <jeevan(dot)ladhe(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: fix empty array expression in get_qual_for_list()
Date: 2017-06-26 17:38:19
Message-ID: CAOgcT0NPQeOP38sBaztjVfZTV_cbAJYdAXgH=WkssKQXWoEM+Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 26, 2017 at 8:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Jeevan Ladhe <jeevan(dot)ladhe(at)enterprisedb(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-06-26 17:42:52 Re: Another reason why the recovery tests take a long time
Previous Message nb 2017-06-26 16:57:11 pg_basebackup fails on Windows when using tablespace mapping