From: Mario Weilguni <mweilguni@sime.com>
To: pgsql-performance@postgresql.org
Subject: Re: vacuum locking
Date: Fri, 24 Oct 2003 08:17:22 +0200
Message-ID: <200310240817.22586.mweilguni@sime.com> (raw)
In-Reply-To: <29123.1066915615@sss.pgh.pa.us>
References: <16272.318.870000.93584@gargle.gargle.HOWL>
<200310230814.56738.mweilguni@sime.com>
<29123.1066915615@sss.pgh.pa.us>
Am Donnerstag, 23. Oktober 2003 15:26 schrieb Tom Lane:
> ... 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.
of course both approaches have advantages, it simply depends on the usage
pattern. A case where oracle really rules over postgresql are m<-->n
connection tables where each record consist of two foreign keys, the
overwrite approach is a big win here.
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: mweilguni@sime.com
Subject: Re: vacuum locking
In-Reply-To: <200310240817.22586.mweilguni@sime.com>
* 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