Re: Recovery mode with partitioned tables and ANY(NULL) in WHERE clause

From: Piotr Włodarczyk <piotrwlodarczyk89(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Recovery mode with partitioned tables and ANY(NULL) in WHERE clause
Date: 2019-08-09 16:50:31
Message-ID: CAP-dhMp8BPRK_Vt-=sni+Uek8hO+boXgUEHRvbOkgOYvoKdKRw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thanks for replay Tom,

Can you tell me in which versions it'll be fixed? For me it's critical
situation because we can have some potentially dangerous places in
application.

On Fri, Aug 9, 2019 at 6:45 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> =?UTF-8?Q?Piotr_W=C5=82odarczyk?= <piotrwlodarczyk89(at)gmail(dot)com> writes:
> > I think we found BUG in version from 11.4 to 11.5 (maybe and previous).
>
> Yeah, looks like the ScalarArrayOpExpr path in
> match_clause_to_partition_key forgot to consider the possibility
> of a constant-null array. Will fix, thanks for the report!
>
> regards, tom lane
>

--

Pozdrawiam
Piotr Włodarczyk

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-08-09 17:21:53 Re: Recovery mode with partitioned tables and ANY(NULL) in WHERE clause
Previous Message Tom Lane 2019-08-09 16:45:42 Re: Recovery mode with partitioned tables and ANY(NULL) in WHERE clause