> I have been experimenting with Slony-I (1.1.0) log shipping features.
> That would work for me, but there is one, big problem: when my
> filesystem is full slon daemon writes empty log files instead of
> stopping until normal logging may continue. I thought it is not supposed
> to work this way, so I looked into the sources and found out, that most
> of log write errors are ignored, so one the logs are not reliable. Is is
> really supposed to be that way?

It is certainly supposed to fail when disk errors occur so that you don't
have empty logs.

If you can point out locations of insufficient error checking, that would
be helpful.

I have tried it out with a full disk and found it stopping; it sounds very
rather peculiar that that wouldn't happen for you.

In particular, every time a query is written out (e.g. -
INSERT/UPDATE/DELETE), the return codes are checked, and things roll back
if the writes do not succeed.

There is the possibility that maybe your platform is providing unexpected
return codes; can you detail operating system version, please?