Re: rename

From: Ken Guest <kguest(at)stockbyte(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: rename
Date: 2002-11-27 18:26:02
Message-ID: 3DE50E3A.6010901@stockbyte.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alvaro Herrera wrote:

>On Wed, Nov 27, 2002 at 04:56:39PM +0000, Ken Guest wrote:
>
>
>>Neil Conway wrote:
>>
>>
>>
>>>On Wed, 2002-11-27 at 09:29, Ken Guest wrote:
>>>
>>>
>>>
>>>>Is it possible to rename databases, and what's the syntax I should
>>>>use?
>>>>
>>>>
>>>However, this is not recommended operating procedure, if it destroys all
>>>your data I won't take any responsibility :-) A safer route would be to
>>>pg_dump the database and restore it with a different name.
>>>
>>>
>>so would pg_dump olddb | pgsql newdb work or this is too simplistic an
>>approach?
>>
>>
>
>Yeah, it should work... What do you mean by too simplistic? It is too
>simple so it must be wrong? :-D
>
>
>
Something like that!
Anyways I got it working - much thanks to Neil Conway.
Now I have the strange occurance that creating a gist index:
CREATE INDEX key2img_fr_rdtree_idx on image_fr using gist ( key2img
gist__intbig_ops) with ( islossy );

works on one database (the old, test, one) but not on the new one, I get
this error
ERROR: DefineIndex: opclass "gist__intbig_ops" not found

No errors occurred during the restore process.
What do I need to do to create that index?

k.

________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________

In response to

  • rename at 2002-11-27 14:29:16 from Ken Guest

Browse pgsql-general by date

  From Date Subject
Next Message Johnson, Shaunn 2002-11-27 18:29:35 Re: fatal error in database : UPDATE
Previous Message Johnson, Shaunn 2002-11-27 18:08:23 fatal error in database