Grant McLean wrote:
On Thu, 2005-05-05 at 14:16 -0400, Jeff - wrote:
One of the biggest things for Slony is that you can install slony,
set things up and it will bring the slave(s) up to speed. You
don't need to do an initial data dump (I think you still need to load
the schema on the
On May 5, 2005, at 5:03 PM, Grant McLean wrote:
Why would you need to take anything down to run pg_dump? And surely
bringing a slave up to speed using Slony would be much slower than
dump/restore?
You'd need to stop client access to PG to prevent changes from
occuring between when you take the
Peter Wilson wrote:
Grant McLean wrote:
On Thu, 2005-05-05 at 14:16 -0400, Jeff - wrote:
One of the biggest things for Slony is that you can install slony,
set things up and it will bring the slave(s) up to speed. You
don't need to do an initial data dump (I think you still need to
load the
On Fri, May 06, 2005 at 09:01:58AM -0400, Jeff - wrote:
slave and hten fire up dbmirror. Although it might work if you
install the dbmirror triggers, then dump restore.
It's a little trickier than that, but yes, it might work. Somewhere
in my mail archives, I have a very angry rant about
On Thu, May 05, 2005 at 03:35:27PM +0100, Peter Wilson wrote:
Looking at Slony now, can someone tell me what the benefits of Slony are
over DBmirror? As far as I can see:
+ both are async Master-multiple slaves
+ both (I think) can do cascaded replication
This isn't really true of dbmirror.
Andrew Sullivan wrote:
On Thu, May 05, 2005 at 03:35:27PM +0100, Peter Wilson wrote:
Looking at Slony now, can someone tell me what the benefits of Slony are
over DBmirror? As far as I can see:
+ both are async Master-multiple slaves
+ both (I think) can do cascaded replication
This isn't really
[EMAIL PROTECTED] (Jeff -) writes:
On May 5, 2005, at 5:03 PM, Grant McLean wrote:
Why would you need to take anything down to run pg_dump? And surely
bringing a slave up to speed using Slony would be much slower than
dump/restore?
You'd need to stop client access to PG to prevent changes
Peter Wilson wrote:
Andrew Sullivan wrote:
On Thu, May 05, 2005 at 03:35:27PM +0100, Peter Wilson wrote:
Looking at Slony now, can someone tell me what the benefits of Slony
are over DBmirror? As far as I can see:
+ both are async Master-multiple slaves
+ both (I think) can do cascaded
On Fri, May 06, 2005 at 12:09:14PM -0400, Chris Browne wrote:
What I need, for that, is a way of grabbing all the index definitions
for the table. One way to do that would be to run pg_dump -s -t a,
though I'd rather have a method that uses the connection I already
have to the database.
On Fri, May 06, 2005 at 05:42:38PM +0100, Peter Wilson wrote:
I got the lack of schema changes from the Slony documentation.
This seems odd. I see Brad already told you what to look for; but
putting schema changes in through slonik was _always_ part of the
design. What's always been true (and
Vlads thread on Slony against PGcluster made me go back to take another
look at Slony. I'd tried to get it going back in February when I needed
to build some replicated databases. Slony was my first choice because it
seemed to be the current 'hot topic'.
I couldn't get it to work - and having
On May 5, 2005, at 10:35 AM, Peter Wilson wrote:
I couldn't get it to work - and having tried another couple of
solutions I settled on DBMirror which comes with Postgres in the
'contrib' directory.
I've had no issues setting up slony. I've even had it running in a 6
node cluster with no
On Thu, 2005-05-05 at 14:16 -0400, Jeff - wrote:
One of the biggest things for Slony is that you can install slony,
set things up and it will bring the slave(s) up to speed. You
don't need to do an initial data dump (I think you still need to load
the schema on the slaves, but not the
13 matches
Mail list logo
