From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Generic Messages for Logical Decoding |
Date: | 2016-04-06 13:41:55 |
Message-ID: | CANP8+jLGZgm8-_ZM7tdowQmM+2_2Bs+55pPu-crvZbfmgFyZpA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On 6 April 2016 at 14:35, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> > Generic Messages for Logical Decoding
>
> The buildfarm thinks this was a remarkably poor choice of random data
> payload:
>
> SELECT 'žluťoučký kůň' FROM pg_logical_emit_message(true, 'test',
> 'žluťoučký kůň');
> ?column?
> ---------------
> žluťoučký kůň
>
> Since this test is not, so far as I can see, at all interested in
> character encoding questions, I suggest not using non-ASCII data in it.
>
Yes, working on it now.
This was my bad, since I requested it be added.
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2016-04-06 13:56:50 | pgsql: Modify test_decoding/messages to remove non-ascii chars |
Previous Message | Tom Lane | 2016-04-06 13:35:35 | Re: pgsql: Generic Messages for Logical Decoding |