| From: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
|---|---|
| To: | Vik Fearing <vik(at)postgresfriends(dot)org> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, jian he <jian(dot)universality(at)gmail(dot)com>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
| Subject: | Re: Virtual generated columns |
| Date: | 2025-01-08 19:29:51 |
| Message-ID: | CAB-JLwbMeiBkepTiw_zT-19-XjSK6tWP1Efxr2SsRK0r_GHK+w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Em qua., 8 de jan. de 2025 às 16:23, Vik Fearing <vik(at)postgresfriends(dot)org>
escreveu:
> This is lying to the planner, and you get to enjoy whatever breaks
> because of it. A function that accesses external data is not immutable;
> it is stable at best.
>
I understand that, but it's not documented, so users can think that way is
fine. So, it would be good to explain why this way could break this or that.
regards
Marcos
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2025-01-08 19:32:24 | Re: Reorder shutdown sequence, to flush pgstats later |
| Previous Message | Peter Eisentraut | 2025-01-08 19:28:33 | Re: Virtual generated columns |