Re: « The PL/pgSQL interpreter parses the function's source text and produces an internal binary instruction tree... »

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Bryn Llewellyn <bryn(at)yugabyte(dot)com>
Cc: pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: « The PL/pgSQL interpreter parses the function's source text and produces an internal binary instruction tree... »
Date: 2022-07-29 01:23:30
Message-ID: 14BAC5B9-225E-49A8-A225-60C2F179E334@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On Jul 28, 2022, at 18:04, Bryn Llewellyn <bryn(at)yugabyte(dot)com> wrote:
> Is this expected?

Yes. This isn't a bug.

> In other words, is there a careful explanation of what "parse" means in the context of "create or replace" for a subprogram that predicts all of the outcomes that I reported here?

Database objects (such as tables and columns) are left as identifiers until they are executed, because that is the point at which a plan for those statements is created. The other components of PL/pgSQL are translated to internal form (and thus checked for existence) as compile time.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bryn Llewellyn 2022-07-29 01:49:32 Re: « The PL/pgSQL interpreter parses the function's source text and produces an internal binary instruction tree... »
Previous Message Bryn Llewellyn 2022-07-29 01:04:29 « The PL/pgSQL interpreter parses the function's source text and produces an internal binary instruction tree... »