On Fri, Dec 13, 2019 at 03:03:47PM +1300, Thomas Munro wrote: > On Fri, Dec 13, 2019 at 7:05 AM Justin Pryzby <pry...@telsasoft.com> wrote: > > I have a nagios check on ancient tempfiles, intended to catch debris left by > > crashed processes. But triggered on this file: > > > > $ sudo find /var/lib/pgsql/12/data/base/pgsql_tmp -ls > > 142977 4 drwxr-x--- 3 postgres postgres 4096 Dec 12 11:32 > > /var/lib/pgsql/12/data/base/pgsql_tmp > > 169868 4 drwxr-x--- 2 postgres postgres 4096 Dec 7 01:35 > > /var/lib/pgsql/12/data/base/pgsql_tmp/pgsql_tmp11025.0.sharedfileset > > 169347 5492 -rw-r----- 1 postgres postgres 5619712 Dec 7 01:35 > > /var/lib/pgsql/12/data/base/pgsql_tmp/pgsql_tmp11025.0.sharedfileset/0.0 > > 169346 5380 -rw-r----- 1 postgres postgres 5505024 Dec 7 01:35 > > /var/lib/pgsql/12/data/base/pgsql_tmp/pgsql_tmp11025.0.sharedfileset/1.0 > > > > I found: > > 2019-12-07 01:35:56 | 11025 | postgres | canceling statement due to > > statement timeout | CLUSTER > > pg_stat_database_snap USI > > 2019-12-07 01:35:56 | 11025 | postgres | temporary file: path > > "base/pgsql_tmp/pgsql_tmp11025.0.sharedfileset/2.0", size 5455872 | CLUSTER > > pg_stat_database_snap USI > > Hmm. But then... maybe the two log lines you quoted should > be the other way around for that.
And, it's actually the other way around, when I order BY something better than left(log_time::text,19). postgres=# SELECT log_time pid, session_line ln, pid, database db, left(message,99), left(query,33) FROM jrn_postgres_log WHERE user_name IS NOT NULL AND log_time BETWEEN '2019-12-07 01:35' AND '2019-12-07 01:36' ORDER BY 1,2; 2019-12-07 01:35:56.626-06 | 1 | 11025 | postgres | temporary file: path "base/pgsql_tmp/pgsql_tmp11025.0.sharedfileset/2.0", size 5455872 | CLUSTER pg_stat_database_snap USI 2019-12-07 01:35:56.626-06 | 2 | 11025 | postgres | canceling statement due to statement timeout | CLUSTER pg_stat_database_snap USI
