Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> Doug McNaught <doug(at)wireboard(dot)com> writes:
> > Hmmm--AFAIK, VACUUM is supposed to grab locks on the tables it
> > processes, which will block until all open transactions against that
> > table are finished.  So either VACUUM or your transactions will have
> > to wait, but they shouldn't interfere with each other. 
> 
> Upshot: a client holding an open transaction, plus another client trying
> to do VACUUM, can clog up the database for everyone else.

Thanks for the clarification.  But the original poster's problem, that 
VACUUM caused his transactions to fail, theoretically shouldn't
happen--right?

-Doug
-- 
Free Dmitry Sklyarov! 
http://www.freesklyarov.org/ 

We will return to our regularly scheduled signature shortly.

In response to

• Re: Is there a problem running vacuum in the middle of a transaction? at 2001-09-06 05:03:21 from Tom Lane

Responses

• Re: Is there a problem running vacuum in the middle of a transaction? at 2001-09-06 15:13:43 from Tom Lane

pgsql-hackers by date

Next:	From: tomas	Date: 2001-09-06 13:15:26
	Subject: Conditional NOTIFY is not implemented
Previous:	From: D'Arcy J.M. Cain	Date: 2001-09-06 12:33:22
	Subject: Re: Log rotation?