Thread: Error: No one parent tuple was found
Hi!
This is my problem:
uname -a
Linux mail 2.4.18-3 #1 Thu Apr 18 07:37:53 EDT 2002 i686 unknown
xxx=# select version();
version
-------------------------------------------------------------
PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.96
(1 row)
psql -d colabo -c "vacuum full verbose analyze"
NOTICE: --Relation pg_largeobject--
NOTICE: Pages 84730: Changed 68898, reaped 83003, Empty 0, New 0; Tup
948705: Vac 46341, Keep/VTL 0/0, UnUsed 533451, MinLen 44, MaxLen 2092;
Re-using: Free/Avail. Space 52105268/52023388; EndEmpty/Avail. Pages
0/78465.
CPU 3.56s/1.98u sec elapsed 60.15 sec.
NOTICE: Index pg_largeobject_loid_pn_index: Pages 5947; Tuples 948705:
Deleted 3.
CPU 0.17s/0.79u sec elapsed 9.57 sec.
ERROR: No one parent tuple was found
In a mail of the 12 of August Tom Lane say that this problem is solved in
version 7.3 but so far I cannot make the update.
In that same mail, Tom proposes to do
psql -d colabo -c "select * from pg_largeobject for update;"
But...
"Apr 28 11:16:45 mail kernel: Out of Memory: Killed process 12168 (psql)."
So wath can i do?
Thanks!!!
Sergio
Please, somebody can help me? Regards, Sergio > -----Mensaje original----- > De: Sergio Pili [SMTP:sergio.pili@spm.com.ar] > Enviado el: Lunes 28 de Abril de 2003 16:08 > Para: 'pgsql-general@postgresql.org' > CC: 'Marcos Suarez' > Asunto: [GENERAL] Error: No one parent tuple was found > > Hi! > > This is my problem: > > uname -a > Linux mail 2.4.18-3 #1 Thu Apr 18 07:37:53 EDT 2002 i686 unknown > > xxx=# select version(); > version > ------------------------------------------------------------- > PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.96 > (1 row) > > > > psql -d colabo -c "vacuum full verbose analyze" > > NOTICE: --Relation pg_largeobject-- > NOTICE: Pages 84730: Changed 68898, reaped 83003, Empty 0, New 0; Tup > 948705: Vac 46341, Keep/VTL 0/0, UnUsed 533451, MinLen 44, MaxLen 2092; > Re-using: Free/Avail. Space 52105268/52023388; EndEmpty/Avail. Pages > 0/78465. > CPU 3.56s/1.98u sec elapsed 60.15 sec. > NOTICE: Index pg_largeobject_loid_pn_index: Pages 5947; Tuples 948705: > Deleted 3. > CPU 0.17s/0.79u sec elapsed 9.57 sec. > ERROR: No one parent tuple was found > > In a mail of the 12 of August Tom Lane say that this problem is solved in > version 7.3 but so far I cannot make the update. > In that same mail, Tom proposes to do > > psql -d colabo -c "select * from pg_largeobject for update;" > > But... > > "Apr 28 11:16:45 mail kernel: Out of Memory: Killed process 12168 (psql)." > > > So wath can i do? > > > Thanks!!! > > Sergio > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly
Try select loid, pageno from pg_largeobject for update or even select loid, pageno, substr(data from 1 for 1) I don't see why the second version would do anything different to the first but it might be worth a try. -- Nigel J. Andrews On Tue, 29 Apr 2003, Sergio Pili wrote: > Please, somebody can help me? > > Regards, > Sergio > > > -----Mensaje original----- > > De: Sergio Pili [SMTP:sergio.pili@spm.com.ar] > > Enviado el: Lunes 28 de Abril de 2003 16:08 > > Para: 'pgsql-general@postgresql.org' > > CC: 'Marcos Suarez' > > Asunto: [GENERAL] Error: No one parent tuple was found > > > > Hi! > > > > This is my problem: > > > > uname -a > > Linux mail 2.4.18-3 #1 Thu Apr 18 07:37:53 EDT 2002 i686 unknown > > > > xxx=# select version(); > > version > > ------------------------------------------------------------- > > PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.96 > > (1 row) > > > > > > > > psql -d colabo -c "vacuum full verbose analyze" > > > > NOTICE: --Relation pg_largeobject-- > > NOTICE: Pages 84730: Changed 68898, reaped 83003, Empty 0, New 0; Tup > > 948705: Vac 46341, Keep/VTL 0/0, UnUsed 533451, MinLen 44, MaxLen 2092; > > Re-using: Free/Avail. Space 52105268/52023388; EndEmpty/Avail. Pages > > 0/78465. > > CPU 3.56s/1.98u sec elapsed 60.15 sec. > > NOTICE: Index pg_largeobject_loid_pn_index: Pages 5947; Tuples 948705: > > Deleted 3. > > CPU 0.17s/0.79u sec elapsed 9.57 sec. > > ERROR: No one parent tuple was found > > > > In a mail of the 12 of August Tom Lane say that this problem is solved in > > version 7.3 but so far I cannot make the update. > > In that same mail, Tom proposes to do > > > > psql -d colabo -c "select * from pg_largeobject for update;" > > > > But... > > > > "Apr 28 11:16:45 mail kernel: Out of Memory: Killed process 12168 (psql)." > > > > > > So wath can i do? > > > > > > Thanks!!! > > > > Sergio > >
Sergio Pili <sergio.pili@spm.com.ar> writes:
>> psql -d colabo -c "vacuum full verbose analyze"
>> ERROR: No one parent tuple was found
AFAIK this can only happen if you have open transactions in parallel
with the VACUUM FULL. Killing off the open transactions should allow
the VACUUM to complete. See today's "Still getting VACUUM errors"
thread over in pgsql-admin.
BTW, if you cannot update to 7.3, at least update to 7.2.4 --- there are
some pretty nasty bugs in 7.2.1.
regards, tom lane
Tom,
>AFAIK this can only happen if you have open transactions in
parallel
>with the VACUUM FULL. Killing off the open transactions should
allow
>the VACUUM to complete. See today's "Still getting VACUUM errors"
>thread over in pgsql-admin.
It is rare since only one batch process open transaction and insert large
objects, and this process is not running at the moment of the vacuum, all
the other accesses are readings with out transactions...
there is some form to know if there are transactions open?
Thanks
Sergio