Re: Recovery mode with partitioned tables and ANY(NULL) in WHERE clause
piotrwlodarczyk89@gmail.com
From: Piotr Włodarczyk <piotrwlodarczyk89@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Date: 2019-08-09T17:23:10Z
Lists: pgsql-bugs
Cool, thanks! pt., 9 sie 2019, 19:21 użytkownik Tom Lane <tgl@sss.pgh.pa.us> napisał: > =?UTF-8?Q?Piotr_W=C5=82odarczyk?= <piotrwlodarczyk89@gmail.com> writes: > > 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. > > Unfortunately this just missed this week's releases, so it'll be the > next quarterly releases in November. > > If you're sufficiently worried about it you could apply the patch locally. > It's pretty trivial: > > > https://git.postgresql.org/pg/commitdiff/2f729d83226705d1149419a2aef7c1678fe641ec > > regards, tom lane >
Commits
-
Fix SIGSEGV in pruning for ScalarArrayOp with constant-null array.
- 59d3789294cf 12.0 landed
- 2f729d832267 11.6 landed
- 0662eb6219f1 13.0 landed