| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Adrien Nayrat <adrien(dot)nayrat(at)anayrat(dot)info> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18097: Immutable expression not allowed in generated at |
| Date: | 2024-09-25 16:48:01 |
| Message-ID: | 11596.1727282881@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Adrien Nayrat <adrien(dot)nayrat(at)anayrat(dot)info> writes:
> I see. So I understand we were lucky it worked before the commit added
> the check of volatility in generated column ?
Pretty much. There are other cases that could trigger expansion
of such a function before the restore is complete. It is unfortunate
that this bit you in a minor release, but there are lots of other
ways you could have tripped over the missing dependency unexpectedly.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-09-25 20:33:42 | Re: BUG #18627: Regression (15 -> 16) - Join removal not performed when join condition spans multiple tables |
| Previous Message | Adrien Nayrat | 2024-09-25 16:36:45 | Re: BUG #18097: Immutable expression not allowed in generated at |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Westermann (DWE) | 2024-09-25 16:52:47 | src/backend/optimizer/util/plancat.c -> Is this correct English |
| Previous Message | Adrien Nayrat | 2024-09-25 16:36:45 | Re: BUG #18097: Immutable expression not allowed in generated at |