RE: Best way to keep track of a sliced TOAST

idea? You've mentioned that the current jsonb format is byte-oriented. Does that imply that a single jsonb key value might be split between multiple chunks? Bruno Hass De: Robert Haas Enviado: sexta-feira, 15 de março de 2019 12:22 Para: Bruno Hass Cc: pgs

RE: Best way to keep track of a sliced TOAST

_ De: Robert Haas Enviado: terça-feira, 12 de março de 2019 14:34 Para: Bruno Hass Cc: pgsql-hackers Assunto: Re: Best way to keep track of a sliced TOAST On Mon, Mar 11, 2019 at 9:27 AM Bruno Hass wrote: > I've been reading about TOASTing and would like to modify how the

Best way to keep track of a sliced TOAST

ced TOASTs. This idea, however, was pointed to me to be a rather naive approach. What would be the best way to do this? Bruno Hass

GSoC 2019 - TOAST'ing in slices idea

Hello everyone, I am currently writing my proposal for GSoC 2019 for the TOAST'ing in slices idea. I already have a sketch of the description and approach outline, which I am sending in this e-mail. I would be happy t

[Proposal] TOAST'ing in slices

rmore, I have a couple of questions: * Would it be a good idea to modify the TOAST table row to keep metadata on the data it stores? * This proposal will modify how JSONB, array and text fields are TOASTed. Where can I find the code related to that? Kind regards, Bruno Hass Postg

GSoC 2019 - TOAST'ing in slices idea

Hello everyone, I am currently writing my proposal for GSoC 2019 for the TOAST'ing in slices idea. I already have a sketch of the description and approach outline, which I am sending in this e-mail. I would be happy to