7;t have an issue
(for our case, we really just need the json data with an identifier telling
us that the row changed, we're not doing full logical replication).
Best,
Colin
On Wed, Feb 7, 2018 at 4:18 PM, Tomas Vondra
wrote:
> On 02/07/2018 09:07 PM, Colin Morelli wrote:
> > Appe
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
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
