Re: parallel.c is not marked as test covered - Mailing list pgsql-hackers

From Robert Haas
Subject Re: parallel.c is not marked as test covered
Date
Msg-id CA+Tgmoac+sysZi0QKtexCKwQ99fjiwfrbQJ4aom-i1C0s6SeAg@mail.gmail.com
Whole thread Raw
In response to Re: parallel.c is not marked as test covered  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: parallel.c is not marked as test covered  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Fri, Jun 10, 2016 at 1:49 PM, Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> Regarding the patch that ended up being committed, I wonder if it is
> intentional that PL/pgSQL overwrites the context from the parallel worker.
> Shouldn't the context effectively look like
>
> ERROR:  message
> CONTEXT:  parallel worker
> CONTEXT:  PL/pgSQL function
>
> Elsewhere in this thread I suggested getting rid of the parallel worker
> context by default (except for debugging), but if we do want to keep it,
> then it seems to be a bug that a PL/pgSQL function can just eliminate it.

Several people have suggested getting rid of that now, so maybe we
should just go ahead and do it.

How would we make it available for debugging, though?  That seems like
something people will want.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Reviewing freeze map code
Next
From: Robert Haas
Date:
Subject: Re: [sqlsmith] Failed assertion in postgres_fdw/deparse.c:1116