Yes, pgsql_tmp, you ought to be looking for a sudden and drastic jump in space utilization around the time of the error message. You're not concerned with the current space utilization, but with the one around that time, because, it probably got freed right after the error was raised. How many times has this happened ? what kind of queries were running at that time? can you identify something that could have required lots of temporary space?
Am Mo., 10. Dez. 2018 um 17:33 Uhr schrieb Ron <ronljohnso...@gmail.com>: > Which file system (specifically, which directory)? Is it > data/base/pgsql_tmp? There's 96GB free, which is 74% of the volume. > > On 12/10/2018 04:50 PM, Rene Romero Benavides wrote: > > Maybe the temp space got released right after the failure? > > https://grokbase.com/t/postgresql/pgsql-general/02ag7k8gcr/tuplestore-write-failed > do you have space usage charts for that partition? doesn't it show a spike > during that time? > > Am Mo., 10. Dez. 2018 um 15:54 Uhr schrieb Ron <ronljohnso...@gmail.com>: > >> There's certainly a problem with the application, but the error is in the >> pg_log, not the application log. >> >> On 12/10/2018 03:21 PM, Rene Romero Benavides wrote: >> >> What if this error message pertains to something happening on the >> application side? >> >> Am Mo., 10. Dez. 2018 um 09:56 Uhr schrieb Ron <ronljohnso...@gmail.com>: >> >>> Hi, >>> >>> v9.6.6 >>> >>> >>> 2018-12-07 06:21:55.504 EST 10.140.181.89(35868) CDS CDSLBXW 13748 >>> SELECT >>> PostgreSQL JDBC Driver 53100 ERROR: could not write to tuplestore >>> temporary >>> file: No space left on device >>> >>> I see this in the pg_log file, but #1 can't figure out what "tuplestore" >>> is >>> (Google doesn't help), and #2 there's lots of space on all my file >>> systems. >>> data/base, where pgsql_tmp lives, has 96GB free.) >>> >>> Thanks >>> >>> >> > -- > Angular momentum makes the world go 'round. > -- El genio es 1% inspiración y 99% transpiración. Thomas Alva Edison http://pglearn.blogspot.mx/
