Hi Andrew

I thank you for the reply, your suggestions are quite good, but it is 
still not possible for me to convince my CHEF to adapt SLONY-I in the 
prod. env. because of the non sync.-ed data in case of a failover .

My question is :

IS IT POSSIBLE TO CONFIGURE SLONY-I SO THAT :
- DML changes will be commited on the Master only after they are 
SYNC.-ed to the slave.
- I mean it is better for me (if my data-records will not be written on 
the master), than (written on master and missed on the slave after a 
failover as example) .
- Knowing that : - I work with a SLON Sync-Interval of  500 msec and 
will reduce it now to 100 msec


Thanks for the answer in advance
Largo.

--------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------

Andrew Sullivan schrieb:
> On Tue, Oct 17, 2006 at 04:59:38PM +0200, Largo wrote:
>   
>> How is it possible to log all the changes I did to the DB in a file ; 
>>     
>
> There are two ways I can think of:
>
> 1.	Have your application write redundantly.  This has the
> disadvantage that you can't do this in scope of a transaction.
>
> 2.	Write a trigger function in C or some other untrusted
> language, that writes the deltas out to a file inside the scope of
> the transaction.  This has the danger that it will block your
> application longer, and could cause some transactions to roll back.
>
> But I also wonder what you're protecting against.  If you do either
> of these (and especially, 2), it seems to me you have no more
> protection than just logging everything in your database.  Which is
> what Slony does anyway.  You could lose some transactions if the
> database crashed unrecoverably; but presumably, if the disk is that
> hosed, you'll also find your log file broken.  No?
>
> A
>
>