| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | bernice(dot)southey(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19072: New-style SQL language function referencing a temp table behaves oddly |
| Date: | 2025-10-04 17:26:00 |
| Message-ID: | 1526598.1759598760@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> When created in psql, a new-style SQL language function referencing a temp
> table disappears with the session, as if it were a temporary function.
Yeah, this is expected, since the parser will create a pg_depend
linkage from the function to the temp table.
> When created in pgAdmin, the function survives.
Really? I don't use pgAdmin, but I don't see how it could affect the
object dependency rules. Perhaps it's not closing the originating
session when you think it is?
There is a nearby thread proposing forbidding new-style functions
from having dependencies on temp objects [1]. Curious to know if
you think that'd be a good answer.
regards, tom lane
[1] https://www.postgresql.org/message-id/flat/19cf6ae1-04cd-422c-a760-d7e75fe6cba9%40uni-muenster.de
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bernice Southey | 2025-10-04 20:02:15 | Re: BUG #19072: New-style SQL language function referencing a temp table behaves oddly |
| Previous Message | Tom Lane | 2025-10-04 17:17:37 | Re: [BUGS] BUG #11500: PRIMARY KEY index not being used |