Re: [HACKERS] pg_stat_tmp files for dropped databases

2014-03-05 Thread Alvaro Herrera
Tomas Vondra wrote: > On 22.2.2014 01:13, Thom Brown wrote: > > I've noticed that files for dropped databases aren't removed from > > pg_stat_tmp. After a cluster-wide VACUUM ANALYSE, and restarting > > Postgres, all the old database pg_stat_tmp files remain. > Yeah, that's a bug in pgstat_recv_

Re: [HACKERS] pg_stat_tmp files for dropped databases

2014-02-21 Thread Thom Brown
On 22 February 2014 01:07, Tomas Vondra wrote: > Hi, > > On 22.2.2014 01:13, Thom Brown wrote: > > Hi, > > > > I've noticed that files for dropped databases aren't removed from > > pg_stat_tmp. After a cluster-wide VACUUM ANALYSE, and restarting > > Postgres, all the old database pg_stat_tmp fil

Re: [HACKERS] pg_stat_tmp files for dropped databases

2014-02-21 Thread Tomas Vondra
Hi, On 22.2.2014 01:13, Thom Brown wrote: > Hi, > > I've noticed that files for dropped databases aren't removed from > pg_stat_tmp. After a cluster-wide VACUUM ANALYSE, and restarting > Postgres, all the old database pg_stat_tmp files remain. > > Shouldn't these be cleaned up? Yeah, that's a

[HACKERS] pg_stat_tmp files for dropped databases

2014-02-21 Thread Thom Brown
Hi, I've noticed that files for dropped databases aren't removed from pg_stat_tmp. After a cluster-wide VACUUM ANALYSE, and restarting Postgres, all the old database pg_stat_tmp files remain. Shouldn't these be cleaned up? -- Thom