Re: BUG #18097: Immutable expression not allowed in generated at

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Aleksander Alekseev <aleksander@timescale.com>

Cc: pgsql-hackers@lists.postgresql.org, James Keener <jim@jimkeener.com>

Date: 2023-11-14T17:48:54Z

Lists: pgsql-bugs, pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Ensure we preprocess expressions before checking their volatility.
- f07a3039c72b 16.2 landed
- abd1b1325d60 12.18 landed
- 9bd0f74eac19 14.11 landed
- 9057ddbefe7e 15.6 landed
- 743ddafc7124 17.0 landed
- 5c11104c7d20 13.14 landed

Aleksander Alekseev <aleksander@timescale.com> writes:
>> There are a couple of points worth bikeshedding perhaps.  I didn't
>> spend much thought on the wrapper functions' names, but it's surely
>> true that the semantic difference between contain_mutable_functions
>> and ContainMutableFunctions is quite un-apparent from those names.
>> Anybody got a better idea?

> Oh no! We encountered one of the most difficult problems in computer
> science [1].

Indeed :-(.  Looking at it again this morning, I'm thinking of
using "contain_mutable_functions_after_planning" --- what do you
think of that?

			regards, tom lane