MIME-Version: 1.0
References: <CAN-LCVMq2X=fhx7KLxfeDyb3P+BXuCkHC0g=9GF+JD4izfVa0Q@mail.gmail.com>
 <CAJ7c6TNAYyeMYKVkiwOZChy7UpE_CkjpYOk73gcWTXMkLkEyzw@mail.gmail.com>
 <CAEze2WibtT+EdGscamqDm3+7qauWi_S6nVUhbK_qg1rkqN_48w@mail.gmail.com>
 <CA+TgmoaVcjUkmtWdc_9QjBzvSShjDBYk-5XFNaOvYLgGROjJMA@mail.gmail.com> <ZG1XjI5meIvQNS/+@paquier.xyz>
In-Reply-To: <ZG1XjI5meIvQNS/+@paquier.xyz>
From: Nikita Malakhov <hukutoc@gmail.com>
Date: Wed, 24 May 2023 12:16:50 +0300
Message-ID: <CAN-LCVO_G9o4Ry16WzNU3+0CWvj3PkDXFaJNdK1yiU-ia+V6YQ@mail.gmail.com>
Subject: Re: RFI: Extending the TOAST Pointer
To: Michael Paquier <michael@paquier.xyz>
Cc: Robert Haas <robertmhaas@gmail.com>, 
	Matthias van de Meent <boekewurm+postgres@gmail.com>, 
	Aleksander Alekseev <aleksander@timescale.com>, 
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000813bb705fc6cf708"
Archived-At: <https://www.postgresql.org/message-id/CAN-LCVO_G9o4Ry16WzNU3%2B0CWvj3PkDXFaJNdK1yiU-ia%2BV6YQ%40mail.gmail.com>
Precedence: bulk

--000000000000813bb705fc6cf708
Content-Type: text/plain; charset="UTF-8"

Hi!

I've made a WIP patch that uses 64-bit TOAST value ID instead of 32-bit,
and sent it as a part of discussion, but there was no feedback on such a
solution. There was a link to that discussion at the top of this thread.

Also, I have to note that, based on our work on Pluggable TOAST - extending
TOAST pointer with additional structures would require review of the logical
replication engine, currently it is not suitable for any custom TOAST
pointers.
Currently we have no final solution for problems with logical replication
for
custom TOAST pointers.

-- 
Regards,
Nikita Malakhov
Postgres Professional
The Russian Postgres Company
https://postgrespro.ru/

--000000000000813bb705fc6cf708
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi!<div><br></div><div>I&#39;ve made a WI=
P patch that uses 64-bit TOAST value ID instead of 32-bit,</div><div>and se=
nt it as a part of discussion, but there was no feedback on such a</div><di=
v>solution. There was a link to that discussion at the top of this thread.<=
/div></div><div><br></div>Also, I have to note that, based on our work on P=
luggable TOAST - extending<div>TOAST pointer with additional structures wou=
ld require review of the logical</div><div>replication engine,=C2=A0current=
ly it is not suitable for any custom TOAST pointers.</div><div>Currently we=
 have no final solution for problems with logical replication for</div><div=
>custom TOAST pointers.<br><div class=3D"gmail_quote"><div dir=3D"ltr" clas=
s=3D"gmail_attr"><br></div></div><span class=3D"gmail_signature_prefix">-- =
</span><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div=
 style=3D"color:rgb(34,34,34)">Regards,</div><div style=3D"color:rgb(34,34,=
34)">Nikita Malakhov<br></div><div style=3D"color:rgb(34,34,34)">Postgres P=
rofessional</div><div style=3D"color:rgb(34,34,34)">The Russian Postgres Co=
mpany</div><div style=3D"color:rgb(34,34,34)"><a href=3D"https://postgrespr=
o.ru/" target=3D"_blank">https://postgrespro.ru/</a></div></div></div></div=
></div>

--000000000000813bb705fc6cf708--