On 28 Apr 2014 19:29, "Jan Wieck" <jan at wi3ck.info> wrote:
>
> On 04/28/14 08:01, Steve Singer wrote:
>>

Thank you Steve/Jan.

As I said, I was just trying to prevent duplicate row in that way. Not that
it will completely take care of it.


>    since the index isn't restricted to the primary key columns of the
>    tAble. And since it is shared by all user tables, that's impossible.
>

How about capturing primary key value in catalogs like its done for
relation OID?
(Its a last guess :) )

> 3) It will also no t prevent something like this:
>
>
>     insert into dtest values (1, 'D');
>     -- wait for 30 minutes in which slony cleanup switches logs and
>     -- the index corruption happens
>
>     insert into dtest values (1, 'D');
>

This is the next case i was thinking , it becomes difficult in my case too
to find duplicate row in sl_log_N.

I belive this type of scenario should be described somewhere in slony faq
for user reference.

-Raghav
>
> Regards,
> Jan
>
>
>
> --
> Jan Wieck
> Senior Software Engineer
> http://slony.info
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20140428/a563f620/attachment.htm