Re: [ADMIN] Power outage borked things (8.1.10)...

2008-03-02 Thread Bruce Momjian
Hannes Dorbath wrote: > Michael Monnerie wrote: > > On Mittwoch, 20. Februar 2008 Tom Lane wrote: > >> 5. Figure out why a simple power failure was able to do this to you, > >> and fix it. The most likely bet is that your disk drives are lying > >> about write completion ... see the PG archives fo

[ADMIN] Is my vacuumdb stuck in a loop?

2008-03-02 Thread Michael Goldner
I'm running Postgres 8.1.8 on RHEL. I have a very large database that consists of a single table with a large object column. The table had just under 2 million rows. The database looks to be about 700GB is size. I have autovacuum running on the system and performance had been good. I'm not sur

Re: [ADMIN] Is my vacuumdb stuck in a loop?

2008-03-02 Thread Tom Lane
"Michael Goldner" <[EMAIL PROTECTED]> writes: > Am I stuck in a loop, or is this happening because the size of the relation > is so large that postgres is operating on smaller chunks? It's removing as many dead rows at a time as it can handle. Arithmetic suggests that you've got maintenance_work_

Re: [ADMIN] Is my vacuumdb stuck in a loop?

2008-03-02 Thread Michael Goldner
On 3/2/08 11:15 AM, "Tom Lane" <[EMAIL PROTECTED]> wrote: > "Michael Goldner" <[EMAIL PROTECTED]> writes: >> Am I stuck in a loop, or is this happening because the size of the relation >> is so large that postgres is operating on smaller chunks? > > It's removing as many dead rows at a time as it

Re: [ADMIN] Is my vacuumdb stuck in a loop?

2008-03-02 Thread Tom Lane
Michael Goldner <[EMAIL PROTECTED]> writes: >> The fact that there are so many dead large objects is what I'd be >> worrying about. Does that square with your sense of what you've >> removed, or does it suggest you've got a large object leak? Do you >> use contrib/lo and/or contrib/vacuumlo to ma

Re: [ADMIN] Power outage borked things (8.1.10)...

2008-03-02 Thread Hannes Dorbath
Bruce Momjian wrote: We have a new section added in 8.3 for exactly that: That's great, I missed it. May I suggest to add a warning about LVM, EVMS, DRBD and Linux MD RAID 5? All do currently not support write barriers and are therefor not safe with volatile write caches below. -- Best reg

Re: [ADMIN] Latest postgres stable version

2008-03-02 Thread Bruce Momjian
Ron Mayer wrote: > Tom Lane wrote: > >> On Tue, Feb 26, 2008 at 12:08 AM, Suresh Gupta VG <[EMAIL PROTECTED]> > >> wrote: > >>> May I know what is the stable pgsql release and latest? > > > > This topic has been addressed very recently, see this thread: > > http://archives.postgresql.org/pgsql-ad