Re: [COMMITTERS] pgsql: Generic Messages for Logical Decoding

2016-04-07 Thread Fujii Masao
On Thu, Apr 7, 2016 at 1:47 PM, Andres Freund wrote: > On 2016-04-07 12:26:28 +0900, Fujii Masao wrote: >> In my example, the WAL record of INSERT that I executed last should be in >> 00010005. But pg_xlogdump could not display that. >> The output of pg_xlogdump was: >> >> $ pg_xlo

Re: [COMMITTERS] pgsql: Generic Messages for Logical Decoding

2016-04-06 Thread Andres Freund
On 2016-04-07 12:26:28 +0900, Fujii Masao wrote: > In my example, the WAL record of INSERT that I executed last should be in > 00010005. But pg_xlogdump could not display that. > The output of pg_xlogdump was: > > $ pg_xlogdump data/pg_xlog/00010005 > pg_xlogdump: F

Re: [COMMITTERS] pgsql: Generic Messages for Logical Decoding

2016-04-06 Thread Fujii Masao
On Thu, Apr 7, 2016 at 12:06 AM, Andres Freund wrote: > > > On April 6, 2016 5:00:54 PM GMT+02:00, Fujii Masao > wrote: >>On Wed, Apr 6, 2016 at 6:08 PM, Simon Riggs >>wrote: >>> Generic Messages for Logical Decoding >>> >>> API and mechanism to allow generic messages to be inserted into WAL >>

Re: [COMMITTERS] pgsql: Generic Messages for Logical Decoding

2016-04-06 Thread Andres Freund
On April 6, 2016 5:00:54 PM GMT+02:00, Fujii Masao wrote: >On Wed, Apr 6, 2016 at 6:08 PM, Simon Riggs >wrote: >> Generic Messages for Logical Decoding >> >> API and mechanism to allow generic messages to be inserted into WAL >that are >> intended to be read by logical decoding plugins. This c

Re: [COMMITTERS] pgsql: Generic Messages for Logical Decoding

2016-04-06 Thread Fujii Masao
On Wed, Apr 6, 2016 at 6:08 PM, Simon Riggs wrote: > Generic Messages for Logical Decoding > > API and mechanism to allow generic messages to be inserted into WAL that are > intended to be read by logical decoding plugins. This commit adds an optional > new callback to the logical decoding API. W

Re: [COMMITTERS] pgsql: Generic Messages for Logical Decoding

2016-04-06 Thread Simon Riggs
On 6 April 2016 at 14:35, Tom Lane wrote: > Simon Riggs 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?

Re: [COMMITTERS] pgsql: Generic Messages for Logical Decoding

2016-04-06 Thread Tom Lane
Simon Riggs 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ůň Sin

Re: [COMMITTERS] pgsql: Generic Messages for Logical Decoding

2016-04-06 Thread Michael Paquier
On Wed, Apr 6, 2016 at 6:08 PM, Simon Riggs wrote: > Generic Messages for Logical Decoding > > API and mechanism to allow generic messages to be inserted into WAL that are > intended to be read by logical decoding plugins. This commit adds an optional > new callback to the logical decoding API. >

[COMMITTERS] pgsql: Generic Messages for Logical Decoding

2016-04-06 Thread Simon Riggs
Generic Messages for Logical Decoding API and mechanism to allow generic messages to be inserted into WAL that are intended to be read by logical decoding plugins. This commit adds an optional new callback to the logical decoding API. Messages are either text or bytea. Messages can be transaction