Received: from sunpine.krs.ru (SunPine.krs.ru [195.161.16.37]) by hub.org (8.9.3/8.9.3) with ESMTP id UAA30071 for ; Mon, 9 Aug 1999 20:55:31 -0400 (EDT) (envelope-from vadim@krs.ru) Received: from krs.ru (dune.krs.ru [195.161.16.38]) by sunpine.krs.ru (8.8.8/8.8.8) with ESMTP id IAA12029; Tue, 10 Aug 1999 08:50:20 +0800 (KRSS) Sender: root@sunpine.krs.ru Message-ID: <37AF774C.F2F43D1C@krs.ru> Date: Tue, 10 Aug 1999 08:50:20 +0800 From: Vadim Mikheev Organization: OJSC Rostelecom (Krasnoyarsk) X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Tom Lane CC: Herouth Maoz , Matthew Hagerty , pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] Proper use of Transactions... References: <23213.934207520@sss.pgh.pa.us> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Tom Lane wrote: > > Even if the backend itself crashes, an uncommitted transaction will > remain uncommitted, since no entry saying it's committed ever gets > written to pg_log. Any tuples the dead backend did manage to write out > will look like not-yet-committed tuples until the end of time. > > BTW, I am not sure whether VACUUM ever realizes it can reclaim those > uncommitted tuples. To do that it'd have to make some kind of It does. Vadim