Postgre internal temporary schemas could be filtered out

PG in some conditions generates (and dont destroy later) some temporary schemas (like: pg_temp_x, pg_toast_temp_x). In HeidiSQL connected database content tree (left pane) lists them all because of query: SELECT "nspname" FROM "pg_catalog"."pg_namespace" ORDER BY "nspname";

Will it ruin something if query is changed to: SELECT "nspname" FROM "pg_catalog"."pg_namespace" WHERE "nspname" not ilike 'pg_temp%' and "nspname" not ilike 'pg_toast_temp%' ORDER BY "nspname"; to avoid screen waste? There may be schemas before pg_t* and after, so it need scrolling over "wasteland".

NB! Schema pg_catalog is valuable to see. It has sometimes interesting things inside :)

That query was modified a few times, and in the end I added an exclude-filter in the advanced session settings for that purpose:

wonderful :)

Gentlemen,

It is quite illogical that after all of this period of time, that you do not have a User Manual or User Guide. Those of you who do not see the need for beginner's to have some type of orientation; need to be residing on another planet.

None of us came into this world knowing anything. There are those who pick new ideas and different procedures up very quickly (kudos to those). Then, there are "old farts" like me, who need a carrot in front of them in order to energize them into motion.

If I could, I would certainly ask for assistance to document something, but at 87 years old, that will be too much of a demand on me.

Someone out there, please come to the aid of "dumb ass beginners" - like me.

Bert Conliffe

@bercon Did you know there's a general help document available? See the "Help" menu at the top right here.

Apart from that, you're welcome to ask questions here. I guess I can answer most of your HeidiSQL related questions, as I'm still 40 years younger 😁