Re: SQL-standard function body - Mailing list pgsql-hackers

From Andres Freund
Subject Re: SQL-standard function body
Date
Msg-id 20200630192606.brfidtzwjrftcum2@alap3.anarazel.de
Whole thread Raw
In response to SQL-standard function body  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: SQL-standard function body  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,

On 2020-06-30 19:49:04 +0200, Peter Eisentraut wrote:
> The function body is parsed at function definition time and stored as
> expression nodes in probin.  So at run time, no further parsing is
> required.

As raw parse tree or as a parse-analysed tree? I assume the latter?

Isn't a consequence of that that we'd get a lot more errors if any DDL
is done to tables involved in the query? In contrast to other languages
we'd not be able to handle column type changes etc, right?

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: warnings for invalid function casts
Next
From: Andres Freund
Date:
Subject: Re: pg_bsd_indent compiles bytecode