Re: Bug in Physical Replication Slots (at least 9.5)?

From: Greg Stark <stark(at)mit(dot)edu>
To: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Jonathon Nelson <jdnelson(at)dyn(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Bug in Physical Replication Slots (at least 9.5)?
Date: 2018-01-19 11:28:58
Message-ID: CAM-w4HMU==SkHHzS6KDSrNiKU9vk2R4TG73M4FJzA-8Yui34+g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On 19 January 2017 at 09:37, Kyotaro HORIGUCHI
<horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>
> Though I haven't look closer to how a modification is splitted
> into WAL records. A tuple cannot be so long. As a simple test, I
> observed rechder->xl_tot_len at the end of XLogRecordAssemble
> inserting an about 400KB not-so-compressable string into a text
> column, but I saw a series of many records with shorter than
> several thousand bytes.

I think the case to check is a commit record with many thousands of
subtransactions. I'm not sure you can fill a whole segment though.

--
greg

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Sergey Burladyan 2018-01-19 14:18:43 Re: BUG #15006: "make check" error if current user is "user"
Previous Message Greg Clough 2018-01-19 11:23:47 RE: BUG #15016: Pgadmin 4_2.1 BUG

Browse pgsql-hackers by date

  From Date Subject
Next Message Marco Nenciarini 2018-01-19 11:37:36 Re: [PATCH] Logical decoding of TRUNCATE
Previous Message Simon Riggs 2018-01-19 10:31:47 Re: [PATCH] session_replication_role = replica with TRUNCATE