Mon Aug 16 08:53:49 PDT 2010
- Previous message: [Slony1-general] Drop Node command works, but leaves crumbs behind.
- Next message: [Slony1-general] Update the column with same value
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hackers, Is there any specific reason to generate an UPDATE query (in LogTrigger) when both the old and new value are the same? Can't we ignore the replication of this particular row silently? I am referring to the following comment in slony1_funcs.c /* * It can happen that the only UPDATE an application does is to set a * column to the same value again. In that case, we'd end up here with * no columns in the SET clause yet. We add the first key column here * with it's old value to simulate the same for the replication * engine. */ Thanks, Sivakumar.K -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20100816/7f4ebb51/attachment.htm
- Previous message: [Slony1-general] Drop Node command works, but leaves crumbs behind.
- Next message: [Slony1-general] Update the column with same value
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list