| From: | "Euler Taveira" <euler(at)eulerto(dot)com> |
|---|---|
| To: | Seebs <seebs(at)seebs(dot)net> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: index access method documentation light on details on ii_AmCache |
| Date: | 2023-09-14 13:06:03 |
| Message-ID: | 6ba13314-2d5d-4828-ad49-0bb46775a027@app.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wed, Sep 13, 2023, at 6:48 PM, Seebs wrote:
> On Wed, 13 Sep 2023 15:48:41 -0300
> "Euler Taveira" <euler(at)eulerto(dot)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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Seebs | 2023-09-14 16:00:11 | Re: index access method documentation light on details on ii_AmCache |
| Previous Message | Seebs | 2023-09-13 21:48:22 | Re: index access method documentation light on details on ii_AmCache |