| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Matteo Sgalaberni <sgala(at)sgala(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: database bloat,non removovable rows, slow query |
| Date: | 2006-09-01 20:01:42 |
| Message-ID: | 1157140902.4786.34.camel@state.g2switchworks.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, 2006-09-01 at 12:28, Matteo Sgalaberni wrote:
> On Fri, Sep 01, 2006 at 10:43:30AM -0400, Tom Lane wrote:
> > Matteo Sgalaberni <sgala(at)sgala(dot)com> writes:
> > > 22 daemons that have a persistent connection to this database(all
> > > connection are in "idle"(no transaction opened).
> >
> > You may think that, but you are wrong.
> Ok. I stopped all clients. No connections to this database. Only psql
> console. Made vacuum
> full/freeze all cominations... again dead rows non removable. Nothing
> changed as in production.
>
> this is my postgres config:
>
> http://pastebin.com/781480
>
> I read a lot about bloat tables related to
> not appropriate fsm settings... can be the mine a case of
> misconfiguration of these parameters?
Something is holding a lock, somewhere.
Have you tried shutting down and restarting the database to see if you
can get it to vacuum that way? You're not in a transaction in psql,
right?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2006-09-01 20:02:41 | Re: increasing shared buffers: how much should be removed from OS filesystem cache? |
| Previous Message | Merlin Moncure | 2006-09-01 19:49:43 | Re: increasing shared buffers: how much should be removed from OS filesystem cache? |