From: | Florian Schaetz <Florian(dot)Schaetz(at)Optitool(dot)DE> |
---|---|
To: | "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
Subject: | Problem: Temporary tables not really temporary tables |
Date: | 2015-02-10 08:46:08 |
Message-ID: | 01E7E8E50C98824E9045DFD5FFC859D4032F5D7D2FBB@SBSRV.ot.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Hello,
I've got a little problem with my postgresql/postgis server here: Sometimes, temporary tables (sessions?) seem to "survive", which in the end leads to a shared memory error, that can only be resolved by restarting (for a moment). This stops the shared memory error for a moment, but the sessions (and with them, the tables) are still there, even if there aren't any open connections left.
Ironically, rebooting the server completely does NOT resolve it all, only restarting the database does. I assume that the error occurs when the connection to a client closes incorrectly or something like that...
In the end I have to clean up the whole mess manually with...
drop schema pg_temp_<sess_id> cascade;
But how can I prevent such sessions to survive or at least have them cleaned up automatically?
Regards,
Flo
From | Date | Subject | |
---|---|---|---|
Next Message | daku.sandor | 2015-02-10 09:04:00 | Re: How to get some table entries from backup instance back to production instance |
Previous Message | Marcel Ruff | 2015-02-10 08:39:25 | How to get some table entries from backup instance back to production instance |