git.postgresql.org Git - users/c2main/postgres.git/commit

projects / users / c2main / postgres.git / commit

author	Alvaro Herrera <alvherre@alvh.no-ip.org>
	Wed, 31 Mar 2021 21:45:17 +0000 (18:45 -0300)
committer	Alvaro Herrera <alvherre@alvh.no-ip.org>
	Wed, 31 Mar 2021 21:45:25 +0000 (18:45 -0300)
commit	a6d3dea8e5e0c8a0df2f95d66b6c3903a4354ca0
tree	0f2e5fbdb95f588f9f9dc3dac3cf9179c9221d81	tree
parent	9e20406dd847d0f8c1cbd803786c6d0ad33bcbdd	commit \| diff

Disable force_parallel_mode in libpq_pipeline

Some buildfarm animals with force_parallel_mode=regress were failing
this test because the error is reported in a parallel worker quicker
than the rows that succeed.

Take the opportunity to move the SET of lc_messages out of the traced
section, because it's not very interesting.

Diagnosed-by: Tom Lane <tgl@sss.pgh.pa.us>
Discussion: https://postgr.es/m/3304521.1617221724@sss.pgh.pa.us

Cedric's Stuff

RSS Atom

src/test/modules/libpq_pipeline/libpq_pipeline.c		diff \| blob \| blame \| history
src/test/modules/libpq_pipeline/traces/disallowed_in_pipeline.trace		diff \| blob \| blame \| history
src/test/modules/libpq_pipeline/traces/multi_pipelines.trace		diff \| blob \| blame \| history
src/test/modules/libpq_pipeline/traces/pipeline_abort.trace		diff \| blob \| blame \| history
src/test/modules/libpq_pipeline/traces/prepared.trace		diff \| blob \| blame \| history
src/test/modules/libpq_pipeline/traces/simple_pipeline.trace		diff \| blob \| blame \| history
src/test/modules/libpq_pipeline/traces/singlerow.trace		diff \| blob \| blame \| history
src/test/modules/libpq_pipeline/traces/transaction.trace		diff \| blob \| blame \| history