Re: SQL functions, INSERT/UPDATE/DELETE RETURNING, and triggers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: SQL functions, INSERT/UPDATE/DELETE RETURNING, and triggers
Date: 2006-10-12 19:13:11
Message-ID: 16221.1160680391@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Jim C. Nasby" <jim(at)nasby(dot)net> writes:
> Sure, it's just a lot of data to be shuffling around if we can avoid it.
> Perhaps we could only do this if there's triggers on the table involved?

Maybe, but it's awfully late in the 8.2 cycle to be worrying about
performance improvements for something that currently doesn't work at all.
I'm inclined to keep it simple for now; we can revisit the issue later
if anyone has problems in practice.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Neil Conway 2006-10-12 19:16:18 Re: [PATCHES] Documentation fix for --with-ldap
Previous Message Peter Eisentraut 2006-10-12 19:11:24 Re: [PATCHES] Documentation fix for --with-ldap