| From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Nikita Malakhov <hukutoc(at)gmail(dot)com> |
| Subject: | Re: RFI: Extending the TOAST Pointer |
| Date: | 2023-05-18 13:11:57 |
| Message-ID: | CAJ7c6TPbu5hK3=jpTnr_xmtPL5kWi-0B1STyJzGdAOwkvTVFBw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
> I agree that va_tag can have another use. But since we are going to
> make varatt_external variable in size (otherwise I don't see how it
> could be really **extendable**) I don't think this is the right
> approach.
On second thought, perhaps we are talking more or less about the same thing?
It doesn't matter what will be used as a sign of presence of a varint
bitmask in the pointer. My initial proposal to use ToastCompressionId
for this is probably redundant since va_tag > 18 will already tell
that.
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2023-05-18 14:23:08 | The documentation for READ COMMITTED may be incomplete or wrong |
| Previous Message | Pavel Luzanov | 2023-05-18 13:07:22 | Re: psql: Add role's membership options to the \du+ command |