| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, James Keener <jim(at)jimkeener(dot)com> |
| Subject: | Re: BUG #18097: Immutable expression not allowed in generated at |
| Date: | 2023-11-15 15:15:55 |
| Message-ID: | 2661435.1700061355@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Aleksander Alekseev <aleksander(at)timescale(dot)com> writes:
>>> 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?
> It's better but creates an impression that the actual planning will be
> involved.
True, but from the perspective of the affected code, the question is
basically "did you call expression_planner() yet". So I like this
naming for that connection, whereas something based on "transformation"
doesn't really connect to anything in existing function names.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2023-11-15 15:58:57 | Re: BUG #18097: Immutable expression not allowed in generated at |
| Previous Message | PG Bug reporting form | 2023-11-15 13:00:01 | BUG #18200: Undefined behaviour in interval_div |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anthonin Bonnefoy | 2023-11-15 15:20:04 | Re: POC: Extension for adding distributed tracing - pg_tracing |
| Previous Message | Tom Lane | 2023-11-15 15:09:06 | Re: Some performance degradation in REL_16 vs REL_15 |