Egor Chindyaskin

@jrgemignani, I was able to reproduce this bug in a different way using pgreplay utility. To reproduce bug follow steps: ``` *** configure and install pgreplay *** *** then replay...

Yes, test fail occurs without this env variable aswell. I've checked this recently ```shell for i in `seq 1000000`;do echo "iter $i";make -s installcheck || break;done ``` regression.diffs: ```diff diff...

@rafsun42 Thank you! I have tested PR #1483. I have understood how to reproduce the issue faster. If you run tests on a virtual machine exactly with 2 cores, the...

@rafsun42 , i5-12400F, Ubuntu 22.04

@rafsun42 I got around to this test again. I tried setting the debug_parallel_query parameter to regress and it worked for apache age 16 and master. For versions 11 to 15,...

@rafsun42 Thank you. I noticed that this is not the only query that can cause the "CONTEXT: parallel worker" message to appear, so I decided to set this option for...

@jrgemignani Hello! You can get the presented error when upgrading from any version to any, my message contains only the fastest reproduction of the problem when Postgres is updated on...

@jrgemignani As documentation says "pg_upgrade allows data stored in PostgreSQL data files to be upgraded to a later PostgreSQL major version without the data dump/restore typically required for major version...

@jrgemignani Thanks for the clarification, but it turns out that there is no way for people with a petabyte of graphs to upgrade to a major release?

@sda399 Hi, The issue is still relevant as some customers with large databases may have a problem when upgrading to a major version.