luda posch <ludaludaluda at gmail.com> writes:
> I want to be able to see specifically what sql statements pertain to which SYNC
> events.  It does not look like either of my log tables have any relation to the
> sl_event.ev_seqno, although I do see in the log tables things that look like
> that is where the information i am looking for is (ie: log_cmdtype,
> log_cmddata)
>
> I thought that log_actionseq would pertain to sl_event.ev_seqno, but no entires
> exist in my logs where log_actionseq=ev_seqno, so I am confused.
>
> does anybody know where to find this information?
>
> (I am not looking for an algorithm to convert log_cmdtype and log_cmddata into
> SQL statements, I am looking for the location of the specific information
> pertaining to a SYNC event.)

Definitely nontrivial.

The association is that a SYNC consists of all the transactions with
XIDs that are:
 a) After the previous SYNC
 b) Before the current SYNC
 c) Not outstanding in the current SYNC 
 d) Possibly from before the previous SYNC, but committed after that
    SYNC.

[Possibly that's not a perfect explanation...  The query that computes
the relationship between a SYNC and the sl_log_* entries for it is
pretty gory!]

If you look at recent bug #167
http://www.slony.info/bugzilla/show_bug.cgi?id=167

It addresses how to get at this information.

Jan revised the code that presently computes the query that pulls
sl_log_* entries; that material is almost certainly useful for your
analysis.

The way the query is computed is definitely not trivial :-).
-- 
output = ("cbbrowne" "@" "ca.afilias.info")
Christopher Browne
"Bother,"  said Pooh,  "Eeyore, ready  two photon  torpedoes  and lock
phasers on the Heffalump, Piglet, meet me in transporter room three"