Skip site navigation (1) Skip section navigation (2)

Re: Error: No one parent tuple was found

From: Sergio Pili <sergio(dot)pili(at)spm(dot)com(dot)ar>
To: 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Error: No one parent tuple was found
Date: 2003-04-29 16:12:40
Message-ID: 069B887B914BD51180420004AC33E2E80A47843E@MAILSVR_A (view raw or whole thread)
Lists: pgsql-general

	>AFAIK this can only happen if you have open transactions in
	>with the VACUUM FULL.  Killing off the open transactions should
	>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? 



pgsql-general by date

Next:From: David LinkDate: 2003-04-29 16:26:30
Subject: Re: RESOLUTION: pq_recvbuf: unexpected EOF
Previous:From: scott.marloweDate: 2003-04-29 15:51:13
Subject: Re: Importing from Access 2000?

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group