On Mon, Oct 29, 2007 at 12:53:00PM -0400, Andrew Sullivan wrote:
> You don't take the _database_ down, you take the application down.

all applications using the database. which is (at the very least to
end-user) the same as if i did take the database down.

the distinction is of course there, but it's useful for technological
distinction - for user standpoint it's indistinguishable.

> No, it doesn't.  That's exactly the problem.  It looks like it to a
> user, but Slony uses the SPI facility to avoid overhead, which means
> that it _can't_ know about these changes.  There is work afoot to
> make it more possible (see other messages about this), but those
> changes won't be backward compatible.  Now that we have reasonably
> stable releases that support older versions, we may be in a position
> to add backward incompatible features (we did that to 7.3, for
> instance, recently).  But up until 8.3, the features you need to
> achieve what you want just weren't there anyway.

ok, i've practically never wrote anything using spi, so i'm off the base
here. if you say it will become possible with 8.3, and some future,
yet-to-be-written version of slony - it's fair enough. it's good to know
that the developers know about the issue and are doing something about
it.

depesz

-- 
quicksil1er: "postgres is excellent, but like any DB it requires a
highly paid DBA.  here's my CV!" :)
http://www.depesz.com/ - blog dla ciebie (i moje CV)