On Wed, Mar 20, 2019 at 9:20 PM Bruno Hass wrote:
> I would like to optimize the jsonb key access operations. I could not find
> the discussion you've mentioned, but I am giving some thought to the idea.
>
> Instead of storing lengths, could we dedicate the first chunk of the TOASTed
> jsonb to
ql-hackers
Assunto: Re: Best way to keep track of a sliced TOAST
On Fri, Mar 15, 2019 at 7:37 AM Bruno Hass wrote:
> This idea is what I was hoping to achieve. Would we be able to make
> optimizations on deTOASTing just by storing the chunk lengths in chunk 0?
I don't know. I guess we
On Fri, Mar 15, 2019 at 7:37 AM Bruno Hass wrote:
> This idea is what I was hoping to achieve. Would we be able to make
> optimizations on deTOASTing just by storing the chunk lengths in chunk 0?
I don't know. I guess we could also NOT store the chunk lengths and
just say that if you don't know
_
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
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 slicing
> works by taking into consideration the type of the varlena field. These
> changes would support future implementations of type specific optimized
> TOAST'ing functions
Hi,
I've been reading about TOASTing and would like to modify how the slicing works
by taking into consideration the type of the varlena field. These changes would
support future implementations of type specific optimized TOAST'ing functions.
The first step would be to add information to the TO
