Horton

Re: FailedAssertion on partprune

Alvaro Herrera <alvherre@2ndquadrant.com>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Jaime Casanova <jaime.casanova@2ndquadrant.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2018-08-16T16:37:57Z
Lists: pgsql-hackers 
On 2018-Jul-23, Jaime Casanova wrote:


> I was trying sqlsmith on REL_11_STABLE (commit
> 1b957e59b92dc44c14708762f882d7910463a9ac) with a database i have at
> hand, and got an assertion failure.
> It seems to happen during planning on prunning time but only when
> tables get bigger than certain size.

Hi Jaime

Did you try your luck running sqlsmith after this fix?  It'd be
interesting to know if there are further failures.

Thanks for the report,

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Remove bogus Assert in make_partitionedrel_pruneinfo().

  2. LLVMJIT: Adapt to API changes in gdb and perf support.

  3. Rewrite the code that applies scan/join targets to paths.