Re: Duplicate Workers entries in some EXPLAIN plans - Mailing list pgsql-hackers

From Georgios Kokolatos
Subject Re: Duplicate Workers entries in some EXPLAIN plans
Date
Msg-id 157908310389.709.10701676612887031531.pgcf@coridan.postgresql.org
Whole thread Raw
In response to Re: Duplicate Workers entries in some EXPLAIN plans  (Maciek Sakrejda <m.sakrejda@gmail.com>)
Responses Re: Duplicate Workers entries in some EXPLAIN plans
List pgsql-hackers
The following review has been posted through the commitfest application:
make installcheck-world:  tested, failed
Implements feature:       not tested
Spec compliant:           not tested
Documentation:            not tested

The current version of the patch (v2) applies cleanly and does what it says on the box.

> Any thoughts on what we should do with text mode output (which is
untouched right now)? The output Andres proposed above makes sense to
me, but I'd like to get more input.

Nothing to add beyond what is stated in the thread.

>  Sort Method: external merge  Disk: 4920kB
>  Buffers: shared hit=682 read=10188, temp read=1415 written=2101
>  Worker 0: actual time=130.058..130.324 rows=1324 loops=1
>    Sort Method: external merge  Disk: 5880kB
>    Buffers: shared hit=337 read=3489, temp read=505 written=739
>  Worker 1: actual time=130.273..130.512 rows=1297 loops=1
>    Buffers: shared hit=345 read=3507, temp read=505 written=744
>    Sort Method: external merge  Disk: 5920kB

This proposal seems like a fitting approach. Awaiting for v3 which
will include the text version. May I suggest a format yaml test case?
Just to make certain that no regressions occur in the future.

Thanks,

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal: type info support functions for functions that use"any" type
Next
From: Paul Guo
Date:
Subject: Re: standby recovery fails (tablespace related) (tentative patch and discussion)