| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Jan Behrens <jbe-mlist(at)magnetkern(dot)de> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: search_path for PL/pgSQL functions partially cached? |
| Date: | 2025-01-05 01:40:25 |
| Message-ID: | CAKFQuwYTsfYmw9TNiXH=r2WUvDo7QpS+jtYAxK3an2OG7anpMA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Saturday, January 4, 2025, Jan Behrens <jbe-mlist(at)magnetkern(dot)de> wrote:
>
> I re-read section 41.11.2. on Plan Caching:
>
> "The PL/pgSQL interpreter parses the function's source text and
> produces an internal binary instruction tree the first time the
> function is called (within each session). The instruction tree fully
> translates the PL/pgSQL statement structure,
>
The type of a plpgsql variable is by definition its structure; established
in a statement, so this is actually covered by that paragraph. But I would
be for adding a bit more specific terminology here.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2025-01-05 06:48:56 | Re: search_path for PL/pgSQL functions partially cached? |
| Previous Message | David G. Johnston | 2025-01-05 01:19:22 | Re: search_path for PL/pgSQL functions partially cached? |