Hello Vivek,
Am 2007-12-21 15:59:21, schrieb Vivek Khera:
On Dec 21, 2007, at 11:09 AM, Martijn van Oosterhout wrote:
The usual answer is use slony. You can use it to replicate the 8.0
server onto an 8.1 server. This may take weeks/months/years/whatever
to
synchronise. When the slave
On Mon, Jan 07, 2008 at 12:58:44PM +0100, Michelle Konzack wrote:
except he has large objects, which slony can't replicate.
currently or will this be changed in the future?
Not likely to change in the future, no. Slony uses triggers to manage the
changed rows. We can't fire triggers on
On Jan 8, 2008 9:01 AM, Harald Armin Massa [EMAIL PROTECTED] wrote:
Not likely to change in the future, no. Slony uses triggers to manage the
changed rows. We can't fire triggers on large object events, so there's no
way for Slony to know what happened.
that leads me to a question I
Not likely to change in the future, no. Slony uses triggers to manage the
changed rows. We can't fire triggers on large object events, so there's no
way for Slony to know what happened.
that leads me to a question I often wanted to ask:
is there any reason to create NEW PostgreSQL databases
On Jan 8, 2008, at 9:13 AM, Scott Marlowe wrote:
On Jan 8, 2008 9:01 AM, Harald Armin Massa
[EMAIL PROTECTED] wrote:
Not likely to change in the future, no. Slony uses triggers to
manage the
changed rows. We can't fire triggers on large object events, so
there's no
way for Slony to
On Dec 21, 2007 8:53 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi
I am trying to upgrade my database from 8.0 to 8.1 and am looking for a
little info/advice.
This is a production database that we are migrating and it is in CONSTANT
use, so the maintenance window must be small and
Hi
I am trying to upgrade my database from 8.0 to 8.1 and am looking for a
little info/advice.
This is a production database that we are migrating and it is in CONSTANT
use, so the maintenance window must be small and hopefully mostly off-hours.
We use a PITR/LVM snapshot solution for our
On Fri, Dec 21, 2007 at 10:53:49AM -0500, [EMAIL PROTECTED] wrote:
I am trying to upgrade my database from 8.0 to 8.1 and am looking for a
little info/advice.
This is a production database that we are migrating and it is in CONSTANT
use, so the maintenance window must be small and hopefully
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
The problem with pg_restore is that our database takes 3+ weeks to restore
from a dump file. This is not an acceptable window for us. ( Approximately
3 days of this is data + lobs, and the rest indexes and constraints. If we
are doing something
[EMAIL PROTECTED] wrote:
Hi
I am trying to upgrade my database from 8.0 to 8.1 and am looking for a
little info/advice.
This is a production database that we are migrating and it is in CONSTANT
use, so the maintenance window must be small and hopefully mostly off-hours.
We use a PITR/LVM
On Dec 21, 2007, at 11:09 AM, Martijn van Oosterhout wrote:
The usual answer is use slony. You can use it to replicate the 8.0
server onto an 8.1 server. This may take weeks/months/years/whatever
to
synchronise. When the slave is up to date, you pull the plug on the
8.0
server and get
11 matches
Mail list logo
