On Tue, Sep 26, 2006 at 11:00:56AM +0200, Csaba Nagy wrote: > Of course there might be other problems too. Another thing would be that the read-only transaction still needs a snapshot, and whatever transaction ID it uses will have been used by the server also. I think the visibility issue may be solvable as long as the transaction ID on the slave doesn't pass the VACUUM horizon of the server. But it would require careful studying of the WAL write order to be confident it would actually work. Have a nice day, -- Martijn van Oosterhout <kleptog@xxxxxxxxx> http://svana.org/kleptog/ > From each according to his ability. To each according to his ability to litigate.
Attachment:
signature.asc
Description: Digital signature
