Thread: Problem when temp_tablespace get full?
Context…
A query almost filled a SSD drive (temp_tablespace) and my PC got unresponsive;
I did SELECT pg_cancel_backend(6600); 6600 was the pid of the process and got a successful answer (t)
However, just after that, the disk simply turned off and the system crashed.
I was able to restart the PC – The SSD drive and the data are still there but the drive keeps going off without warning.
I know I will have to change my drive!-)
But ma question is: What append the temp_tablespace drive get full?
Daniel
A query
But ma question is: What append the temp_tablespace drive get full?
Sorry, my question might not have been clear…
I set myself the temp_tablespace to that location but did not expect the drive could get full;
Multiple factors may have caused the drive to turn off (not necessarily postgresql);
So, if that temp_tablespace gets full, how postgresql will react/manage the situation?
Daniel
From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of David G. Johnston
Sent: June-03-15 11:54
To: Daniel Begin
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Problem when temp_tablespace get full?
On Wed, Jun 3, 2015 at 11:14 AM, Daniel Begin <jfd553@hotmail.com> wrote:
A query
OK...
But ma question is: What append the temp_tablespace drive get full?
The query, probably...
"There is also a temp_tablespaces parameter, which determines the placement of temporary tables and indexes, as well as temporary files that are used for purposes such as sorting large data sets."
David J.
Am 2015-06-03 19:00, schrieb Daniel Begin: > Sorry, my question might not have been clear… > > I set myself the temp_tablespace to that location but did not expect > the drive could get full; > > Multiple factors may have caused the drive to turn off (not > necessarily postgresql); > > So, if that temp_tablespace gets full, how postgresql will > react/manage the situation? Queries running out of space in pgsql_tmp will just cancel (and rollback). Jan