From: Greg Stark <gsstark@mit.edu>
To: Rob Nagler <nagler@bivio.biz>
Cc: pgsql-performance@postgresql.org
Subject: Re: vacuum locking
Date: 24 Oct 2003 20:07:57 -0400
Message-ID: <87ekx2uqle.fsf@stark.dyndns.tv> (raw)
In-Reply-To: <16281.41629.69000.492473@gargle.gargle.HOWL>
References: <16272.318.870000.93584@gargle.gargle.HOWL>
<200310230814.56738.mweilguni@sime.com>
<29123.1066915615@sss.pgh.pa.us>
<200310240817.22586.mweilguni@sime.com>
<16281.41629.69000.492473@gargle.gargle.HOWL>
Rob Nagler <nagler@bivio.biz> writes:
> Mario Weilguni writes:
> > 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.
I don't understand why you would expect overwriting to win here.
What types of updates do you do on these tables?
Normally I found using update on such a table was too awkward to contemplate
so I just delete all the relation records that I'm replacing for the key I'm
working with and insert new ones. This always works out to be cleaner code. In
fact I usually leave such tables with no UPDATE grants on them.
In that situation I would have actually expected Postgres to do as well as or
better than Oracle since that makes them both functionally equivalent.
--
greg
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: gsstark@mit.edu, nagler@bivio.biz
Subject: Re: vacuum locking
In-Reply-To: <87ekx2uqle.fsf@stark.dyndns.tv>
* 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