pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mario Weilguni <mweilguni@sime.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: vacuum locking
Date: Thu, 23 Oct 2003 09:26:55 -0400
Message-ID: <29123.1066915615@sss.pgh.pa.us> (raw)
In-Reply-To: <200310230814.56738.mweilguni@sime.com>
References: <16272.318.870000.93584@gargle.gargle.HOWL>
	<x7d6cpcdsr.fsf@yertle.int.kciLink.com>
	<16279.4988.496000.539525@gargle.gargle.HOWL>
	<200310230814.56738.mweilguni@sime.com>

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



view thread (45+ messages)  latest in thread

Message-ID: <29123.1066915615@sss.pgh.pa.us>
Permalink:  ../29123.1066915615@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/29123.1066915615@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, mweilguni@sime.com
  Subject: Re: vacuum locking
  In-Reply-To: <29123.1066915615@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox