Closed ncalero-uy closed 11 months ago
Hi, this is normal, the SQL query is associated to the error "no space left". Normally if there was enough disk space it would not end as error and should be associated to the temporary files generation. Anyway I have found several parsing error with logplex format, they have been fixed in commits d51444a and 5945104.
Hi, I found an issue where the database temp space was exhausted by an SQL, and the pgBadger report is not reporting the SQL causing the problem, despite the SQL is in the log.
In this case, the SQL failed with the error message "ERROR: could not write to file "file_name": No space left on device"
The overall statistics section correctly reports the temp space used and files - it only misses the SQL in the Queries section for temp. Like this:
Attaching the PostgreSQL log file to reproduce the report. It is from a Heroku database. heroku-temp-error-20230703.log