From: | Vadim Mikheev <vadim(at)krs(dot)ru> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Concurrent VACUUM: first results |
Date: | 1999-11-26 05:32:31 |
Message-ID: | 383E1B6F.1A0E08EF@krs.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
> > /*
> > * We have to commit our tuple' movings before we'll truncate
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > * relation, but we shouldn't lose our locks. And so - quick hack:
^^^^^^^^
... or moved tuples may be lost in the case of DB/OS crash etc
that may occur after truncation but before commit...
> > * flush buffers and record status of current transaction as
> > * committed, and continue. - vadim 11/13/96
> > */
> > FlushBufferPool(!TransactionFlushEnabled());
> > TransactionIdCommit(myXID);
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > FlushBufferPool(!TransactionFlushEnabled());
> > }
> >
> > vc_updstats() may be called in the already committed transaction.
>
> Oh, that is tricky that they have committed the transaction and continue
> working in an already committed. Yikes. Any idea why we have to commit
> it early?
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | Vadim Mikheev | 1999-11-26 05:46:33 | Re: [GENERAL] drop/rename table and transactions |
Previous Message | Mike Mascari | 1999-11-26 05:12:31 | Re: AW: [HACKERS] Re: [GENERAL] drop/rename table and transactions |