From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Lonni J Friedman <netllama(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: vacuum is failing |
Date: | 2005-01-04 23:30:43 |
Message-ID: | 21561.1104881443@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Lonni J Friedman <netllama(at)gmail(dot)com> writes:
> ERROR: No one parent tuple was found
> Anyone have any suggestions on how to correct this?
Shut down whatever long-running transaction is hanging around in the
background. You wouldn't be getting this error if vacuum weren't
trying to move a chain of updated tuples, and that can only happen
if there's an old transaction someplace.
Of course, the real fix is to use a newer Postgres. I note this in
the 7.2.4 CVS logs:
2003-01-26 18:09 tgl
* src/backend/access/heap/heapam.c (REL7_2_STABLE): Back-patch
fixes to ensure t_ctid always has correct value (prevents some
instances of 'No one parent tuple' VACUUM error, and perhaps worse
things).
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Pierre-Frédéric Caillaud | 2005-01-05 00:20:50 | Re: hundreds of millions row dBs |
Previous Message | Ron Mayer | 2005-01-04 23:10:51 | Re: PostgreSQL 8.0.0 Release Candidate 3 |