Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: plpgsql replication stored procedure


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: aaron(dot)clauson(at)gmail(dot)com
  • Cc: pgsql-general(at)postgresql(dot)org
  • Subject: Re: plpgsql replication stored procedure
  • Date: Mon, 17 Apr 2006 15:21:47 -0400
  • Message-id: <4358(dot)1145301707(at)sss(dot)pgh(dot)pa(dot)us>

aaron(dot)clauson(at)gmail(dot)com writes:
> I'm trying to write a stored procedure that can capture all the changes
> to a table and record the changes based on the table's primary key.
> I can almost get there but the sticking point is being able to access
> the primary key field of the NEW/OLD record in the trigger stored
> procedure without knowing it's name.

There is no way to write such a generic trigger in plpgsql (and even if
you could, its performance would suck :-().  You could do it in C if
you're sufficiently determined.

			regards, tom lane



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group