I'm not sure if this is really a bug, so I'm posting here instead of pgsql-bugs.
Last night I attempted to make a DDL and DML change through Slony, using the
execute script command. The changes (adding a column and updating some rows)
worked on the master but failed on the slave, with the PG da
Hi
Thanks for you reply.
I change it, because taking the fakt that every server will have slave
replication(as fail over) i decided only to use it. i.e.
I have serve A with database test, and server B is replication database test.
So when i need to partition(meaning to separate 1/2 of the databas
I am using slony1-2.0.3 and needed to make some wholesale changes, so like
other times I stopped all slon processes on my master box as well as on the 2
slave machines. I then dropped the slony schema on all three, completely
removing it, made my changes. I then ran my slonik script at the mas
From: pgsql-admin-ow...@postgresql.org
[mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Uwe Bartels
Sent: Tuesday, June 22, 2010 4:29 PM
To: Kevin Grittner
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] blocking automatic vacuum
# select version();
Found the culprit, the app had thrown locks on the first table in the replicate
set and it was waiting for those locks to be released.
From: Plugge, Joe R.
Sent: Wednesday, June 23, 2010 12:23 PM
To: pgsql-admin@postgresql.org
Subject: Slony - I question
I am using slony1-2.0.3 and needed to ma
Postgres version 8.4.4
Hardware:
12 cpu intel
sda 15K 600GB raid 1
sdb ssd 173GB raid 1 (most tables and indexes on sdb)
adaptec controller
24G of memory
shared buffers 12GB
Machine age 3 months
Normal load 2-4
200-300 Transactions per second
We had a database failure last night after one of
On Fri, 2010-06-25 at 06:31 -0700, Bob Lunney wrote:
> I'm not sure if this is really a bug, so I'm posting here instead of
> pgsql-bugs.
I am thinking this needs to be posted to:
http://lists.slony.info/mailman/listinfo/slony1-general
JD
--
PostgreSQL.org Major Contributor
Command Prompt, In
