Re: No long-lived transaction, still can't delete tuples
| От | Tom Lane | 
|---|---|
| Тема | Re: No long-lived transaction, still can't delete tuples | 
| Дата | |
| Msg-id | 19981.1019689154@sss.pgh.pa.us обсуждение исходный текст | 
| Ответ на | Re: No long-lived transaction, still can't delete tuples (Jeffrey Baker <jwbaker@acm.org>) | 
| Ответы | Re: No long-lived transaction, still can't delete tuples | 
| Список | pgsql-general | 
Jeffrey Baker <jwbaker@acm.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
		
	В списке pgsql-general по дате отправления: