From: | Shaun Thomas <sthomas(at)peak6(dot)com> |
---|---|
To: | Hany ABOU-GHOURY <hghoury(at)gmail(dot)com> |
Cc: | Derrick Rice <derrick(dot)rice(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: PG 9 adminstrations |
Date: | 2011-09-21 12:48:13 |
Message-ID: | 4E79DD0D.3070201@peak6.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice pgsql-performance |
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(at)peak6(dot)com
______________________________________________
See http://www.peak6.com/email-disclaimer/ for terms and conditions related to this email
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-09-21 15:11:18 | Re: query question |
Previous Message | Asli Akarsakarya | 2011-09-21 12:47:23 | a spatial table's bounding box |
From | Date | Subject | |
---|---|---|---|
Next Message | Shaun Thomas | 2011-09-21 13:03:13 | Re: : Performance Improvement Strategy |
Previous Message | Guillaume Cottenceau | 2011-09-21 12:43:07 | Show_database_bloat reliability? [was: Re: REINDEX not working for wastedspace] |