From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tobias Lott <tobias(dot)lott(at)devoteam(dot)com> |
Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: permission denied for pg_temp_XX when vacuuming |
Date: | 2021-03-03 16:33:41 |
Message-ID: | 1194518.1614789221@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tobias Lott <tobias(dot)lott(at)devoteam(dot)com> writes:
> There were no crashes of the instance, but some issues with the connected
> application, resulting in 'could not receive data from client: Connection
> reset by peer' and 'unexpected EOF on client connection with an open
> transaction'.
No, that sort of thing would still allow the backend to shut down cleanly.
> So if this might have left behind temp tables causing the errors, should I
> try to delete these pg_temp tables?
It would definitely be worth looking around to see if you have any temp
tables that shouldn't be there. I think you can just do
\dt pg_temp_*.*
in psql (as superuser) to see what's out there. Figuring out which ones
are live sessions' temp tables might be harder, though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Valeria Kaplan | 2021-03-03 17:23:56 | Re: Code of Conduct: Russian Translation for Review |
Previous Message | Tobias Lott | 2021-03-03 16:26:56 | Re: permission denied for pg_temp_XX when vacuuming |