> > are older than a week, but in such way that they are not deleted from the
> > second DB. Is it possible with slony? Maybe records with certain values in
> > some columns can be ommited from deletion in slave DB?
>
> Andrew Sullivan wrote:
> You can STORE TRIGGER on the second system, that saves those records
> somewhere else.  The obvious way to do this is to use a trigger on the
> replica that INSTEAD copies the records into a _different_, but that doesn't
> fire on DELETE.

So, it is not possible to make those records stay in the replicated
table in slave DB without adding there another table which will gather
data?
Maybe logging trigger could be modified or wrapped somehow, so it
doesn't log certain deletions?

PR