From: | Fabien COELHO <fabien(dot)coelho(at)ensmp(dot)fr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: triggers on prepare, commit, rollback... ? |
Date: | 2008-05-19 15:01:52 |
Message-ID: | alpine.DEB.1.10.0805191633110.5593@briare.cri.ensmp.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dear Tom,
>> trigger on "prepare", "commit", "rollback", "savepoint",
> Yup, and there won't be.
That's a definite answer!
> This has been suggested and rejected before. See the archives.
I'll check into that.
>> It seems to me that such triggers would be useful to help implement a
>> "simple" (hmmm...) synchroneous replication system,
>
> That argument has no credibility whatever.
If you say so.
> We have not even been able to get the replication projects to agree on a
> common set of custom hooks; the chance that they could get by with
> triggers on SQL-visible events is nil.
That is indeed an issue.
On the other hand, there are several possible strategies to implement
replication, but ISTM that all should require a hook (whether SQL visible
or not) at the prepare/commit levels to play around with the 2PC.
Well, thanks for your answer anyway,
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Theo Schlossnagle | 2008-05-19 15:32:28 | DTrace probes. |
Previous Message | Gregory Stark | 2008-05-19 14:22:10 | Re: [HACKERS] WITH RECURSIVE patch V0.1 |