Re: Long text values destroys logical replication slots - Mailing list pgsql-bugs

From Adam Dratwiński
Subject Re: Long text values destroys logical replication slots
Date
Msg-id CAKg6ypJcXr9x4p10gWp217SWG9q=MvB1d702BhAKu9keHrf2iw@mail.gmail.com
Whole thread
In response to Re: Long text values destroys logical replication slots  (Andres Freund <andres@anarazel.de>)
List pgsql-bugs
I managed to reproduce this problem on postgres 9.4.1 and 9.4.5 on osx and gentoo.

On Wed, Oct 28, 2015 at 9:54 PM, Andres Freund <andres@anarazel.de> wrote:
On October 28, 2015 7:51:18 PM GMT+01:00, "Adam Dratwiński" <adam.dratwinski@gmail.com> wrote:
>I recently encountered a bug on my production postgres which results in
>killing replication slot. It happens when there is an UPDATE statement
>called on a record having text column with a very long value (about
>1mb).
>The problem can be easily reproduced by this query:
>
>https://gist.github.com/adwinsky/f7a6dc4382776fb9ea60
>
>Here I am using decoderbufs decoder
>https://github.com/krzychk/decoderbufs
>but it doesn't seems to be related with this plugin as it also happen
>on
>the postgres test decoder.

Did you try the last minor release?

Andres
Hi
---
Please excuse brevity and formatting - I am writing this on my mobile phone.

pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: Long text values destroys logical replication slots
Next
From: ckline@onezero.com
Date:
Subject: BUG #13743: Incorrect default value in documentation for --serviceaccount option to Postgres installer