Wed Jan 12 12:40:20 PST 2005
- Previous message: [Slony1-general] current slony1 limitations
- Next message: [Slony1-general] current slony1 limitations
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Oh, if I changed my oid fields to bytea, slony could replicate them? I have to look into whether bytea would work for our app, of course - I haven't used it before, but having those puppies slony-replicated would be a huge help to me.... Thanks. - DAP >-----Original Message----- >From: slony1-general-bounces at gborg.postgresql.org >[mailto:slony1-general-bounces at gborg.postgresql.org] On Behalf >Of Andrew Sullivan >Sent: Wednesday, January 12, 2005 6:38 AM >To: slony1-general at gborg.postgresql.org >Subject: Re: [Slony1-general] current slony1 limitations > >On Tue, Jan 11, 2005 at 08:17:07PM -0800, Nick Pavlica wrote: >> Are there reliable methods to work around these limitations? > >Sort of. BLOBs, no, although you could use bytea. And you >can propogate schema changes via slonik scripts. > >There are rumours that MySQL's replication occasionally loses >data silently. I haven't tested it. > >A > >-- >Andrew Sullivan | ajs at crankycanuck.ca >In the future this spectacle of the middle classes shocking >the avant- garde will probably become the textbook definition >of Postmodernism. > --Brad Holland >_______________________________________________ >Slony1-general mailing list >Slony1-general at gborg.postgresql.org >http://gborg.postgresql.org/mailman/listinfo/slony1-general >
- Previous message: [Slony1-general] current slony1 limitations
- Next message: [Slony1-general] current slony1 limitations
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list