Re: vacuum locking - Mailing list pgsql-performance

From Tom Lane
Subject Re: vacuum locking
Date
Msg-id 29123.1066915615@sss.pgh.pa.us
Whole thread Raw
In response to Re: vacuum locking  (Mario Weilguni <mweilguni@sime.com>)
Responses Re: vacuum locking  (Rob Nagler <nagler@bivio.biz>)
Re: vacuum locking  (Mario Weilguni <mweilguni@sime.com>)
List pgsql-performance
Mario Weilguni <mweilguni@sime.com> writes:
> I think oracle does not do garbage collect, it overwrites the tuples directly
> and stores the old tuples in undo buffers. Since most transactions are
> commits, this is a big win.

... if all tuples are the same size, and if you never have any
transactions that touch enough tuples to overflow your undo segment
(or even just sit there for a long time, preventing you from recycling
undo-log space; this is the dual of the VACUUM-can't-reclaim-dead-tuple
problem).  And a few other problems that any Oracle DBA can tell you about.
I prefer our system.

            regards, tom lane

pgsql-performance by date:

Previous
From: Allen Landsidel
Date:
Subject: My own performance/tuning q&a
Next
From: Andrew Sullivan
Date:
Subject: Re: vacuum locking