pgsql: Increase parallel bitmap scan test coverage.

Started by Andres Freundabout 9 years ago2 messageshackers
Jump to latest
#1Andres Freund
andres@anarazel.de

Increase parallel bitmap scan test coverage.

Author: Dilip Kumar
Discussion: /messages/by-id/20170331184603.qcp7t4md5bzxbx32@alap3.anarazel.de

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/5a5931533edd2b70bde1f069609f58998dd26fef

Modified Files
--------------
src/test/regress/expected/select_parallel.out | 40 +++++++++++++++++++++++----
src/test/regress/sql/select_parallel.sql | 20 ++++++++++++--
2 files changed, 52 insertions(+), 8 deletions(-)

--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

#2Andres Freund
andres@anarazel.de
In reply to: Andres Freund (#1)
Re: [COMMITTERS] pgsql: Increase parallel bitmap scan test coverage.

On 2017-04-06 20:43:48 +0000, Andres Freund wrote:

Increase parallel bitmap scan test coverage.

Author: Dilip Kumar
Discussion: /messages/by-id/20170331184603.qcp7t4md5bzxbx32@alap3.anarazel.de

This turned the !linux buildfarm red, because it relies on setting
effective_io_concurrency (to increase coverage to the prefetching code).
I plan to wrap the SET in a DO block with an exception handler.

- Andres

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers