Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: fatal error on 8.1 server
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
- Cc: Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-general(at)postgresql(dot)org
- Subject: Re: fatal error on 8.1 server
- Date: Mon, 27 Nov 2006 17:43:32 -0500
- Message-id: <25171(dot)1164667412(at)sss(dot)pgh(dot)pa(dot)us>
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes: > Tony Caduto wrote: >> I did not have autovacuum turned on and I usually do a vacuumdb -z -a -f >> -q each night but this one slipped through the cracks :-( > Strange -- autovacuum should have started an automatic database-wide > vacuum on that database, even if disabled. We only added that in 8.2, no? 8.1 autovacuum would have forced the vacuum to occur, but only if it was enabled in postgresql.conf. regards, tom lane
- References:
- fatal error on 8.1 server
- From: Tony Caduto
- Re: fatal error on 8.1 server
- From: Alvaro Herrera
- Re: fatal error on 8.1 server
- From: Tony Caduto
- Re: fatal error on 8.1 server
- From: Martijn van Oosterhout
- Re: fatal error on 8.1 server
- From: Tony Caduto
- Re: fatal error on 8.1 server
- From: Alvaro Herrera
- fatal error on 8.1 server
- Prev by Date: Re: Unexpected sort order.
- Next by Date: Re: IS it a good practice to use SERIAL as Primary Key?
- Previous by thread: Re: fatal error on 8.1 server
- Next by thread: DB crashed
- Indexes: