[Pgpool-general] Zimbra Detected SpamPgPool replication or Slony

Pascal Cohen pcohen at wimba.com
Mon Nov 26 08:09:47 UTC 2007


> My idea is to keep the DB consistency among the three databases (a kind 
> of two-phase commit). And I just added that row to check the behavior on 
> the three database when an error might occur on a given DB.
> It is like with no-lock I can't guarantee the DB consistency and that 
> with lock I can.
> Am I right ?
> And with the lock, can the update be "accessed" on all the tables only 
> after all the DB have comited their update ?
>   
Oops I think I said some stupid things and mixed lock and prepare 
transaction or something like that ... anyway is there a way to ensure 2 
phase commit with PgPool ?
And it is less clear to me now what role lock plays ...


More information about the Pgpool-general mailing list