diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2019-12-12 13:49:54 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2019-12-12 13:49:54 -0500 |
| commit | 22864f6e02f8fc19f6167442f13d1f917e36548e (patch) | |
| tree | 15bf333a85579d16fcbef0beb2a10c3d64968143 /src/backend/access/gist/gist.c | |
| parent | 1a3efa1eb67ab752231a6fff2743a77ae55808d5 (diff) | |
| download | postgresql-22864f6e02f8fc19f6167442f13d1f917e36548e.tar.gz postgresql-22864f6e02f8fc19f6167442f13d1f917e36548e.zip | |
Put back regression test case in a more robust form.
This undoes my hurried commit 776a2c887, restoring the removed test case
in a form that passes with or without force_parallel_mode = regress.
It turns out that force_parallel_mode = regress simply fails to mask
the Worker lines that will be produced by EXPLAIN (ANALYZE, VERBOSE).
I'd say that's a bug in that feature, as its entire alleged reason
for existence is to make the EXPLAIN output the same. It's certainly
not a bug in the plan node pruning logic. Fortunately, this test case
doesn't really need to use ANALYZE, so just drop that.
Discussion: https://postgr.es/m/18891.1576109690@sss.pgh.pa.us
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions