Andres:
Thanks for the link on the GIT patch code.
I did a big major domo search and found some stuff related to command
triggers:
http://archives.postgresql.org/pgsql-hackers/2012-03/msg00169.php
"Look into the new event triggers started recently." -
Are these command triggers currently in the 9.2.0 code base or is it in
a alpha 9.2.1xxx?
I searched the 9.2.0 code base and found nothing on CREATE TRIGGER that
had anything to do with other than TABLES and VIEWS.
I cannot wait for stable code to arrive, I need to add it today.
Since the hackers group is already working on this, I will not even try
to contribute this work, unless someone wants it.
marco
On 9/21/2012 1:19 PM, Andres Freund wrote:
On Friday, September 21, 2012 08:12:26 PM m...@rpzdesign.com wrote:
Heikki:
Thanks for the response. I am writing an external replication engine
and putting hooks into postgres to send "signals" via a unix socket to
the outside world.
All of the logic and implementation will occur OUTSIDE the postgres
codebase and
will not interfere with any WAL based replication schemes.
The usual "Trigger" level asynch replication does on not suffice since
it does not handle
new databases, new schemas, new tables, new indexes, alter everything,
new functions, etc.
So I started putting into utility.c->xxx_ProcessUtility(..., stmt*
parsetree,....) so that discrete
Does anybody have other ideas where to better locate the "Hooks" for
external replication/signaling
than utility.c?
Look into the new event triggers started recently.
Commits
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=3855968f328918b6cd1401dd11d109d471a54d40
and
3a0e4d36ebd7f477822d5bae41ba121a40d22ccc
Look into earlier discussions around event/command triggers why putting stuff
plainly into ProcessUtility is not all that helpful...
Greetings,
Andres
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
