From: Tom Lane <tgl@sss.pgh.pa.us>
To: Harald Fuchs <hf118@protecting.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Trigger question
Date: Tue, 20 Jan 2004 11:42:30 -0500
Message-ID: <24605.1074616950@sss.pgh.pa.us> (raw)
In-Reply-To: <pufzea4mvw.fsf@srv.protecting.net>
References: <400691EA.96598C34@t1.unisoftbg.com>
<pud69kf3hr.fsf@srv.protecting.net>
<871xpvij42.fsf@mailbox.samurai.com>
<200401200813.57147.dev@archonet.com>
<24300.1074614549@sss.pgh.pa.us>
<pufzea4mvw.fsf@srv.protecting.net>
Harald Fuchs <hf118@protecting.net> writes:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
>> I'm not very clear on
>> how that works myself --- in particular, one would think it important to
>> be able to work with corresponding pairs of OLD and NEW rows, which
>> would be painful with a table-like abstraction.
> Why? If the underlying table has a primary key, finding corresponding
> pairs is trivial; if there isn't, it's impossible.
Exactly. Nonetheless, the correspondence exists --- the UPDATE
definitely updated some particular row of the OLD set into some
particular one of the NEW set. If the trigger API makes it impossible
to reconstruct the matchup, the API is broken.
Even if there is a primary key, the API should not force you to rely
on that; what of an UPDATE that changes the primary key?
regards, tom lane
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, hf118@protecting.net
Subject: Re: Trigger question
In-Reply-To: <24605.1074616950@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