From: | Scott Marlowe <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | Holger Marzen <holger(at)marzen(dot)de> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Subject: bool / vacuum full bug followup |
Date: | 2002-05-03 15:46:56 |
Message-ID: | Pine.LNX.4.33.0205030946190.1594-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 3 May 2002, Holger Marzen wrote:
> On Thu, 2 May 2002, Scott Marlowe wrote:
>
> > And after that, the table started growing after all vacuum fulls. I can't
> > reproduce it now. I blew away the table, recreated it, and now it doesn't
> > do that. I blew away the database, and installed 7.2.1 and it won't do
> > it. I reinstalled 7.2 and blew away the database and it still won't do
> > it.
> >
> > So, I don't know why it WAS doing it, but it isn't now. And of course,
> > it's my personal workstation, so no log files. :-( I'll see if I can
> > reproduce this though, as I've seen similar problems pop up once in the
> > past with a seldom vacuumed database that reached a point where it stopped
> > freeing dead tuples. Very bothersome.
>
> Looks like something that happens only if counters or OIDs are big.
> Possible integer overflow in the vacuum code?
Prior to the test I had been running 100,000 transaction pgbench tests
repeatedly. I'll try running a few million transactions first and see if
the problem surfaces.
Thanks for the suggestions.
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2002-05-03 16:09:15 | Re: making a trigger to a system call to a shell script |
Previous Message | Scott Marlowe | 2002-05-03 15:43:12 | Re: Subject: bool / vacuum full bug followup |