Message-ID: <4E79DD0D.3070201@peak6.com>
Date: Wed, 21 Sep 2011 07:48:13 -0500
From: Shaun Thomas <sthomas@peak6.com>
Reply-To: <sthomas@peak6.com>
Organization: Peak6
User-Agent: Mozilla/5.0 (X11; Linux i686;
	rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Hany ABOU-GHOURY <hghoury@gmail.com>
CC: Derrick Rice <derrick.rice@gmail.com>, <pgsql-performance@postgresql.org>
Subject: Re: PG 9 adminstrations
References: 
 <CAEjHQvk31VQWAONdd_CT80ode4pr+0UvOUy9rqeWuxtX=Dh+Nw@mail.gmail.com>
	<CANvs22EqZABNVKwi-YD-eiBjrC9dwXB5CrkcbEcZFPB+Pqb5uw@mail.gmail.com>
	<CAEjHQvnosXN+RJ5567DynPk+y0-n5fOqcSv0GnjEcBBC=0w2mA@mail.gmail.com>
In-Reply-To: 
 <CAEjHQvnosXN+RJ5567DynPk+y0-n5fOqcSv0GnjEcBBC=0w2mA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
content-transfer-encoding: 7bit

On 09/20/2011 11:29 PM, Hany ABOU-GHOURY wrote:

> Thanks but...did not work different error though
>
> ERROR: relation "history" already exists
> ERROR: relation "idx_history_pagegroupid" already exists
> ERROR: constraint "cdocumentid" for relation "history" already exists

Clearly the history table already exists on your second host. This may 
or may not matter, if the table definitions are the same. If the table 
on host2 was empty, it'll be filled with the data from host1. If not, 
you'll need to truncate the table on host2 first. If you don't want the 
complaints about tables or indexes or constraints that already exist, 
use the -a option for data-only dumps.

Also, might I suggest using the pgsql-novice list? They're more likely 
to help with general issues like this.

-- 
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 800 | Chicago IL, 60604
312-676-8870
sthomas@peak6.com

______________________________________________

See http://www.peak6.com/email-disclaimer/ for terms and conditions related to this email