Re: No long-lived transaction, still can't delete tuples

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeffrey Baker <jwbaker(at)acm(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: No long-lived transaction, still can't delete tuples
Date: 2002-04-24 22:59:14
Message-ID: 19981.1019689154@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jeffrey Baker <jwbaker(at)acm(dot)org> writes:
> 04 begin
> 05 work
> 06 commit
> 07 begin connect
> 08 work begin
> 09 commit delete everything
> 10 begin commit
> 11 work vacuum <= this should get rid of everything < t = 07
> 12 commit disconnect

Actually that vacuum should get rid of everything older than t=10.
What I'm concerned about is this scenario:

client A client B you

begin;
work...
commit;
begin;
take a lunch break...

begin;
work...
commit;

connect
vacuum;

Until client A returns from his lunch break, you'll not be able to
vacuum the trash that client B generated, even though B has committed
his changes.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2002-04-25 00:56:10 Re: [GENERAL] problems with non-trust authentication methods in 7.3devel?
Previous Message Tom Lane 2002-04-24 22:41:41 Re: odd psql behaviour on OSX