Hi,

I am currently researching the capabilities of Slony-l, and have so far
managed to set up a simple example and it works (can be found here
http://www.pgadmin.org/docs/1.4/slony/slonyadmin.html#firstdb
), but unfortunately not in real time (with insert into statements).  Is
this supposed to be the intended behaviour of slony ? and if not how do i
create a subscription set that is always running, and thus always updating
the slave in real time.

The current triggers that slony creates on the table being replicated on
master node:

CREATE TRIGGER _test_logtrigger_1
  AFTER INSERT OR UPDATE OR DELETE
  ON sampledata
  FOR EACH ROW
  EXECUTE PROCEDURE _test.logtrigger('_test', 1, 'kv'); (note: test is my
slony-l cluster name)

And the trigger created on the slave version of the table is:

CREATE TRIGGER _test_denyaccess_1
  BEFORE INSERT OR UPDATE OR DELETE
  ON sampledata
  FOR EACH ROW
  EXECUTE PROCEDURE _test.denyaccess('_test');

I have inserted 1000's of records into the table (on Master Node) after
doing my initial replication, but the changes are never replication to the
slave, do i have to run the script every time i want to replicate ????

If any one can help/advise me, it would be appreciated,

Andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://gborg.postgresql.org/pipermail/slony1-general/attachments/20060818/28690398/attachment.html