Re: checking if jsonb was detoasted and releasing memory - Mailing list pgsql-general

From Tom Lane
Subject Re: checking if jsonb was detoasted and releasing memory
Date
Msg-id 14615.1423753483@sss.pgh.pa.us
Whole thread Raw
In response to checking if jsonb was detoasted and releasing memory  (Igor Stassiy <istassiy@gmail.com>)
List pgsql-general
Igor Stassiy <istassiy@gmail.com> writes:
> Let us say that the datum of type Datum contains a Jsonb* type.
> Then after the call

> Jsonb *jb = DatumGetJsonb(datum);

> the jb might point to a palloc'ed structure, in case detoasting took place.
> So the question is if this is the right way to free up the memory after
> checking that the jb was detoasted?

> if ((void *)jb != DatumGetPointer(datum))
> pfree(jb); // free if detoasted

For the most part the answer is "don't bother".  Except in very narrow
cases, it's not worth it to clean up such values retail as opposed to
letting the next evaluation context reset get rid of them in bulk.

The code you proposed will work, but it's ugly and usually a net waste
of cycles.  It also embeds assumptions we might want to change someday.

            regards, tom lane


pgsql-general by date:

Previous
From: Igor Stassiy
Date:
Subject: checking if jsonb was detoasted and releasing memory
Next
From: Ted Toth
Date:
Subject: 9.5 RLS 'check policy' function arguments