From: Euler Taveira <euler@eulerto.com>
To: Seebs <seebs@seebs.net>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: index access method documentation light on details on ii_AmCache
Date: Thu, 14 Sep 2023 10:06:03 -0300
Message-ID: <6ba13314-2d5d-4828-ad49-0bb46775a027@app.fastmail.com> (raw)
In-Reply-To: <20230913164822.41e4c0bd@seebsdell>
References: <169454016225.2433963.11433530945607791340@wrigleys.postgresql.org>
<a52489dd-e6ca-425b-a23d-d0139728419f@app.fastmail.com>
<20230913164822.41e4c0bd@seebsdell>
On Wed, Sep 13, 2023, at 6:48 PM, Seebs wrote:
> On Wed, 13 Sep 2023 15:48:41 -0300
> "Euler Taveira" <euler@eulerto.com> wrote:
>
> > Unless you change it, ii_Context is CurrentMemoryContext (see
> > makeIndexInfo). Hence, your AM state information is freed when the
> > current memory context is freed.
>
> A thing I am now wondering:
>
> Is there anything in the postgresql documentation which explains this,
> or says when a given memory context will be freed? Like, is the
> ii_Context there for the lifetime of the index? For the lifetime of the
> query? For the lifetime of a single insert operation?
AFAICS there isn't a chapter dedicated to memory contexts in the documentation.
Did you check the README that I pointed out in the previous email? Most of the
developer information is available in README files in the source code. Server
Programming and Internals contain useful information for Postgres hackers too.
--
Euler Taveira
EDB https://www.enterprisedb.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: euler@eulerto.com, seebs@seebs.net, pgsql-docs@lists.postgresql.org
Subject: Re: index access method documentation light on details on ii_AmCache
In-Reply-To: <6ba13314-2d5d-4828-ad49-0bb46775a027@app.fastmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox