pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rob Nagler <nagler@bivio.biz>
To: pgsql-performance@postgresql.org
Subject: Re: vacuum locking
Date: Fri, 24 Oct 2003 16:07:25 -0600
Message-ID: <16281.41629.69000.492473@gargle.gargle.HOWL> (raw)
In-Reply-To: <200310240817.22586.mweilguni@sime.com>
References: <16272.318.870000.93584@gargle.gargle.HOWL>
	<200310230814.56738.mweilguni@sime.com>
	<29123.1066915615@sss.pgh.pa.us>
	<200310240817.22586.mweilguni@sime.com>

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.

That's usually our case.  My company almost always has "groupware"
problems to solve.  Every record has a "realm" (security) foreign key
and typically another key.  The infrastructure puts the security
key on queries to avoid returning the wrong realm's data.

Rob





view thread (45+ messages)  latest in thread

Message-ID: <16281.41629.69000.492473@gargle.gargle.HOWL>
Permalink:  ../16281.41629.69000.492473@gargle.gargle.HOWL/
Also on:    postgresql.org/message-id/16281.41629.69000.492473@gargle.gargle.HOWL

 · 

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: nagler@bivio.biz
  Subject: Re: vacuum locking
  In-Reply-To: <16281.41629.69000.492473@gargle.gargle.HOWL>

* 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