From: Albert REINER <areiner@tph.tuwien.ac.at>
To: pgsql-sql@postgresql.org
Subject: Re: unreferenced primary keys: garbage collection
Date: Wed, 24 Jan 2001 20:36:39 +0100
Message-ID: <20010124203639.A203@frithjof> (raw)
In-Reply-To: <Pine.BSI.4.21.0101240021140.29537-100000@glass.toledolink.com>
References: <d1ms6tgl0kupjbomqgff971e3mljkfoara@4ax.com>
<Pine.BSI.4.21.0101240021140.29537-100000@glass.toledolink.com>
> On Tue, 23 Jan 2001, Forest Wilkinson wrote:
>
> > Jan,
> >
> > Thanks for the reply, but your solution is rather unattractive to me. It
> > requires that, any time a reference to an address id is changed, five
> > tables be searched for the address id. This will create unwanted overhead
If - and I think this is the case for you - it is no problem for you
to have some superfluous adresses in your tables, but you only want to
avoid that those adresses remain there for a long time, you could
simply run the function Jan sent from a cron job. That seems to be
likely to be more efficient not only than the triggers but also to the
ON DELETE RESTRICT solution, I guess.
Trivial, but I HTH -
Albert.
> > Forest Wilkinson wrote:
> > >> > I have a database in which five separate tables may (or may not) reference
> > >> > any given row in a table of postal addresses. I am using the primary /
> > >> > foreign key support in postgres 7 to represent these references.
> > >> >
> > >> > My problem is that, any time a reference is removed (either by deleting or
> > >> > updating a row in one of the five referencing tables), no garbage
> > >> > collection is being performed on the address table. That is, when the
> > >> > last reference to an address record goes away, the record is not removed
> > >> > from the address table. Over time, my database will fill up with
> > >> > abandoned address records.
--
--------------------------------------------------------------------------
Albert Reiner <areiner@tph.tuwien.ac.at>
Deutsch * English * Esperanto * Latine
--------------------------------------------------------------------------
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: areiner@tph.tuwien.ac.at
Subject: Re: unreferenced primary keys: garbage collection
In-Reply-To: <20010124203639.A203@frithjof>
References: <d1ms6tgl0kupjbomqgff971e3mljkfoara@4ax.com> <Pine.BSI.4.21.0101240021140.29537-100000@glass.toledolink.com> <20010124203639.A203@frithjof>
* 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