On Thu, Aug 31, 2017 at 6:23 PM, Thomas Munro <thomas.mu...@enterprisedb.com > wrote:
> Here's a new rebased and debugged patch set. Hi Thomas, I have applied the recent patch (v19) and started testing on this feature and i got a crash with below testcase. with default setting on "postgres.conf" file create table tab1 (a int, b text); create table tab2 (a int, b text); insert into tab1 (select x, x||'_b' from generate_series(1,200000) x); insert into tab2 (select x%20000, x%20000||'_b' from generate_series(1,200000) x); ANALYZE; select * from tab1 t1, tab2 t2, tab1 t3 where t1.a = t2.a and t2.b = t3.b order by 1; WARNING: terminating connection because of crash of another server process DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. HINT: In a moment you should be able to reconnect to the database and repeat your command. server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempting reset: Failed. !> Kindly check, if you can reproduce this at your end. *Thanks & Regards,* *Prabhat Kumar Sahu* Mob: 7758988455 Skype ID: prabhat.sahu1984 www.enterprisedb.co <http://www.enterprisedb.com/>m <http://www.enterprisedb.com/>
