To the best of my knowledge we have not had any DB crashes as yet. I am also replicating the DB using slony, could this be the cause of these weird orphans ? (it is neither of the sl_log_ tables)
Also looking at the timestamps of the files, they all seem to have been created within a very short period of time on the 6th of April
-rw------- 1 postgres postgres 57344 2010-04-06 03:10 110653
-rw------- 1 postgres postgres 0 2010-04-06 03:08 110654
-rw------- 1 postgres postgres 40960 2010-04-06 03:08 110657
-rw------- 1 postgres postgres 8192 2010-04-06 03:08 110658
-rw------- 1 postgres postgres 1073741824 2010-04-06 03:10 110660
-rw------- 1 postgres postgres 1073741824 2010-04-06 03:12 110660.1
-rw------- 1 postgres postgres 1073741824 2010-04-06 03:13 110660.2
-rw------- 1 postgres postgres 1073741824 2010-04-06 03:15 110660.3
-rw------- 1 postgres postgres 1073741824 2010-04-06 03:16 110660.4
-rw------- 1 postgres postgres 1073741824 2010-04-06 03:18 110660.5
-rw------- 1 postgres postgres 1073741824 2010-04-06 03:20 110660.6
-rw------- 1 postgres postgres 1073741824 2010-04-06 03:21 110660.7
-rw------- 1 postgres postgres 26566656 2010-04-06 03:21 110660.8
-rw------- 1 postgres postgres 180224 2010-04-06 03:21 110661
-rw------- 1 postgres postgres 8192 2010-04-06 03:08 110662
-rw------- 1 postgres postgres 8192 2010-04-06 03:08 110663
-rw------- 1 postgres postgres 16384 2010-04-06 03:21 110664
-rw------- 1 postgres postgres 113254400 2010-04-06 03:25 110763
-rw------- 1 postgres postgres 0 2010-04-06 03:25 110765
-rw------- 1 postgres postgres 1073741824 2010-06-03 22:17 112806
