Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [Solved] Postgres performance problem
- From: Vivek Khera <vivek(at)khera(dot)org>
- To: Pgsql performance <pgsql-performance(at)postgresql(dot)org>
- Subject: Re: [Solved] Postgres performance problem
- Date: Fri, 31 Aug 2007 15:36:37 -0400
On Aug 30, 2007, at 2:08 PM, Mark Lewis wrote:
If you're not running regular VACUUMs at all but are instead exclusivelyrunning VACUUM FULL, then I don't think you would see warnings about running out of fsm enties, which would explain why you did not notice the bloat. I haven't confirmed that though, so I might be wrong.
If you run vacuum full, your pages should be full so there should be very small if any number of pages in the free space map. Thus, there would be no warnings.
- References:
- Postgres performance problem
- From: Ruben Rubio
- Re: Postgres performance problem
- From: Chris Mair
- Re: Postgres performance problem
- From: Bill Moran
- Re: Postgres performance problem
- From: ruben
- Re: [Solved] Postgres performance problem
- From: Ruben Rubio
- Re: [Solved] Postgres performance problem
- From: Mark Lewis
- Postgres performance problem
- Prev by Date: Re: 8.2 Autovacuum BUG ?
- Next by Date: Re: 8.2 Autovacuum BUG ?
- Previous by thread: Re: [Solved] Postgres performance problem
- Next by thread: Performance issue
- Indexes: