| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Adam Dratwiński <adam(dot)dratwinski(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Cc: | Krzysiek Kotlarski <kotlarski(dot)krzysztof(at)gmail(dot)com> |
| Subject: | Re: Long text values destroys logical replication slots |
| Date: | 2015-10-28 20:54:34 |
| Message-ID: | 853C54D9-7168-4852-99CF-49DCA1A7B48C@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On October 28, 2015 7:51:18 PM GMT+01:00, "Adam Dratwiński" <adam(dot)dratwinski(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adam Dratwiński | 2015-10-28 21:14:28 | Re: Long text values destroys logical replication slots |
| Previous Message | Adam Dratwiński | 2015-10-28 18:51:18 | Long text values destroys logical replication slots |