Re: large table

From: Luke Coldiron <lukecoldiron(at)hotmail(dot)com>
To: Alan Hodgson <ahodgson(at)simkin(dot)ca>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: large table
Date: 2014-09-22 19:15:27
Message-ID: BAY179-W853E628B9856763B6E3BD4C6B30@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> > From: ahodgson(at)simkin(dot)ca
> > To: pgsql-general(at)postgresql(dot)org
> > Subject: Re: [GENERAL] large table
> > Date: Mon, 22 Sep 2014 11:34:45 -0700
> >
> > On Monday, September 22, 2014 11:17:05 AM Luke Coldiron wrote:
> > > The actual size of the table is around 33 MB.
> > > The myFunc function is called every 2.5 seconds and the wasUpdated function
> > > every 2 seconds by separate processes. I realize that running a FULL VACUUM
> > > or CLUSTER command on the table will resolve the issue but I am more
> > > interested in a root cause that explains why this table would end up in
> > > this state. I have tried to reproduce this issue by running the exact setup
> > > and have not been able to get the table to grow like this example. Any
> > > plausible cause'es or explanations would be much appreciated. Luke
> >
> > I'd guess that some other process held a transaction open for a couple of
> > week, and that prevented any vacuuming from taking place.
> >
Interesting idea, on the surface I'm not sure how this would have happened in the system but I can certainly explore forcing this to happen and see if the result is similar.
> > --
> > Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> > To make changes to your subscription:
> > http://www.postgresql.org/mailpref/pgsql-general

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Luke Coldiron 2014-09-22 19:33:46 Re: large table
Previous Message Bill Moran 2014-09-22 18:38:52 Re: large table