Andrew Sullivan wrote:
> On Mon, Jun 23, 2008 at 05:29:47PM +0200, Cyril SCETBON wrote:
>   
>>> There's no way for Slony to know this.  I agree it would be nice, but it's
>>> simply impossible.  This is a consequence of the way MVCC in Postgres 
>>> works.
>>>  
>>>       
>> I was thinking that simply looking at pg_locks (known for hurting 
>> performance) would help.
>>     
>
> No.
>
> Suppose T1 starts, and then sits there for a while.  It will be in pg_locks
> (because every transaction has one entry), but you don't know what tables
> it's going to touch by looking at that view.
>   
Ok I missed it
But you know in which database the transactions started. So the most 
basic thing is to say if there is no older connection on the database to 
replicate, slony can start , no ?
> Now, Slony comes along and wants to dump the database in a consistent way,
> because it is setting up.  This is the consistent starting point _before
> which_ Slony knows it can ignore transactions (because remember, when you
> set up replication on a table, you created the triggers; but Slony has to
> know what the starting point is in that list of transactions for any given
> replica).  All that Slony can know, then, is whether there are transactions
> prior to itself outstanding.  If the answer is yes, Slony has to wait until
> those transactions commit, so it can be sure that nothing will happen that
> (1) the dump can't see and (2) will never be included in any data sent to
> the target replica.
>   
yes
> That's sort of oversimplifying it, but it's the basic problem.
>   
ok
> A
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
>   

-- 
Cyril SCETBON - Ingénieur bases de données
AUSY pour France Télécom - OPF/PORTAILS/DOP/HEBEX

Tél : +33 (0)4 97 12 87 60
Jabber : cscetbon at jabber.org
France Telecom - Orange
790 Avenue du Docteur Maurice Donat 
Bâtiment Marco Polo C2 - Bureau 202
06250 Mougins
France

***********************************
Ce message et toutes les pieces jointes (ci-apres le 'message') sont
confidentiels et etablis a l'intention exclusive de ses destinataires.
Toute utilisation ou diffusion non autorisee est interdite.
Tout message electronique est susceptible d'alteration. Le Groupe France
Telecom decline toute responsabilite au titre de ce message s'il a ete
altere, deforme ou falsifie.
Si vous n'etes pas destinataire de ce message, merci de le detruire
immediatement et d'avertir l'expediteur.
***********************************
This message and any attachments (the 'message') are confidential and
intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. France Telecom Group shall not be
liable for the message if altered, changed or falsified.
If you are not recipient of this message, please cancel it immediately and
inform the sender.
************************************