Re: parallel workers and client encoding - Mailing list pgsql-hackers

From Robert Haas
Subject Re: parallel workers and client encoding
Date
Msg-id CA+TgmobrwxOXX1W0yUcSYW28QAOCvg8dd4mnauConyJPQQT+Ww@mail.gmail.com
Whole thread Raw
In response to Re: parallel workers and client encoding  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Jun 9, 2016 at 1:47 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Second, if you can't convert an error or notice message (or possibly a
>> notify message) from the server encoding to the client coding, you are
>> definitely going to fail, with or without parallel query, because that
>> conversion has to be done at some stage anyway.
>
> Only if the message gets sent to the client, which it might never be;
> for example because the query is inside a plpgsql exception block that
> traps the error.

Hmm... yeah, OK, that's another case.

> You do have a bug here; please don't argue you don't.

I just said it was a bug in my previous post, so I think it is clear
that I am not arguing that.

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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Don't generate parallel paths for rels with parallel-restricted
Next
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Don't generate parallel paths for rels with parallel-restricted