I am referring to "Temporary tables are automatically dropped at the end of a session, or optionally at the end of the current transaction" (https://www.postgresql.org/docs/18/sql-createtable.html). I.e that if you have to debug a production system, you cannot just look into the temptables to to pin-point where data is not the way expected. You have to recreate every intermediary result.
04.10.2026 22:24:47 Adrian Klaver <[email protected]>: > On 10/4/26 12:27 PM, Thiemo Kellner wrote: >> Hi >> Giving my two dimes. I apologise if some else has given it already. And it >> is quite an operations point of view and mostly based on Oracle. To the best >> of my knowledge, it applies to Postgres even more. >> The data of DB temp tables are not visible outside of the session that has >> put it in. In the case of trying to find the problem of code of functions >> storing intermediary results, they are just not visible for the investigator >> such that one has to do all the steps manually to detect the point where >> things go wrong. In my opinion a real pita. > > I am not quite following the above. > > Do you mean: > > 1) Not having access to the function code ? > > 2) Having access to function code, but not the source of data? > > > > >> Cheers >> Thiemo > > > -- > Adrian Klaver > [email protected]
