On 02/07/2018 10:22 PM, Colin Morelli wrote:
> Hey Tomas,
>
> We're using v1.1.0 of pglogical. I can't honestly say what could
> reproduce this issue as I'm not entirely sure and haven't tested it yet.
>
Well, consider updating - there's 1.1.2 in that exact branch, and
there's also 2.1.1 now.
Hey Tomas,
We're using v1.1.0 of pglogical. I can't honestly say what could reproduce
this issue as I'm not entirely sure and haven't tested it yet.
I had thought it was caused when a toasted row is deleted before the
pglogical_output plugin processes the event (so it fails when going to
de-toast
On 02/07/2018 09:07 PM, Colin Morelli wrote:
> Appears to be a problem with pglogical_output when de-toasting columns.
> Switched to wal2json and the problem went away. I believe I may have
> found the issue anyway. Apologies for the noise.
>
What pglogical version are you using? Can you share an
Appears to be a problem with pglogical_output when de-toasting columns.
Switched to wal2json and the problem went away. I believe I may have found
the issue anyway. Apologies for the noise.
Best,
Colin
On Wed, Feb 7, 2018 at 2:20 PM, Colin Morelli
wrote:
> List,
>
> For seemingly no reason at a
List,
For seemingly no reason at all, my logical replication slot has just
started bailing out with errors every time my client tries to connect to
it. Particularly - at this moment - I'm getting:
2018-02-07 19:14:31 UTC [3985-1] svc_app@app LOG: 0: received
replication command: START_REPLIC
