Hello Marcin,

The Replication of data is activity when some I, U or D is executed, because
Slony is trigger based. So, you can disbled the trigger of the table
"events", and after you have done you work you enable her.

Now, if your table doesn't have a PK, there is a great possibility to have
some error on the replication.

The better way to work is to have a "flag", like "delete", where you can
mark if the tuple is deleted or not, and you don't need to really delete the
record, and you can filtre to show in the user's screen.

Rafael Domiciano
DBA Postgres
Senff Ltda.

2008/6/7 Marcin Kasperski <Marcin.Kasperski at softax.com.pl>:

>
> Let's say I have
>
>    ProductionDatabase ----slony----> ReportDatabase
>
> let's say there is a table - say - "events", which gathers some
> data over time. Let's also say I need all this data in ReportDatabase,
> but only data from last few weeks in ProductionDatabase.
>
> So I'd like to remove old data from "events" in ProductionDatabase,
> but would like to keep them in ReportDatabase.
>
> Is it possible to convince Slony to ignore such a DELETE
>
> (yes, I know, everything bad may happen if I later re-add a row
> with the key matching the removed row, or do sth similar)
>
>
>
> --
> ----------------------------------------------------------------------
> | Marcin Kasperski   | We want to know as early as possible whether
> | http://mekk.waw.pl | the project will succeed. Thus we attack the
> |                    |        high-risk areas first. (Martin)
> ----------------------------------------------------------------------
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20080607/=
0aed5ced/attachment.htm