| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: parallel workers and client encoding |
| Date: | 2016-06-14 02:29:29 |
| Message-ID: | b0e065fa-6393-eea8-524a-59032ab2d5c6@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/9/16 7:16 PM, Tatsuo Ishii wrote:
> Something like SetClientEncoding(GetDatabaseEncoding()) is a Little
> bit ugly. It would be nice if we could have a switch to turn off the
> automatic encoding conversion in the future, but for 9.6, I feel I'm
> fine with your proposed patch.
One way to make this nicer would be to put the encoding of a string into
the StringInfoData structure.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2016-06-14 02:44:06 | Re: Should phraseto_tsquery('simple', 'blue blue') @@ to_tsvector('simple', 'blue') be true ? |
| Previous Message | Peter Eisentraut | 2016-06-14 02:27:24 | Re: parallel workers and client encoding |