From: | ohp(at)pyrenet(dot)fr |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_restore new option -m |
Date: | 2009-02-20 13:44:06 |
Message-ID: | Pine.UW2.4.63.0902201442230.27848@sun.pyrenet |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 19 Feb 2009, Andrew Dunstan wrote:
> Date: Thu, 19 Feb 2009 21:58:18 -0500
> From: Andrew Dunstan <andrew(at)dunslane(dot)net>
> To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> Cc: ohp(at)pyrenet(dot)fr, pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>
> Subject: Re: [HACKERS] pg_restore new option -m
>
>
>
> Tom Lane wrote:
>> ohp(at)pyrenet(dot)fr writes:
>>
>>> pg_restore -C -m 4 -d template1 db.dmp
>>> gives numerous errors, mostly no such relation at index creation time.
>>>
>>
>> You sure you don't get exactly the same without -m?
>>
>
>
>
> Yeah, I have reproduced this. It's because we reconnect to the wrong db in
> this case (i.e. to the -d database, not the created one) in the workers and
> subsequent connects.
>
> I've applied a trivial patch to fix it.
>
works like a charm!
> cheers
>
> andrew
>
>
>
>
thanks
--
Olivier PRENANT Tel: +33-5-61-50-97-00 (Work)
15, Chemin des Monges +33-5-61-50-97-01 (Fax)
31190 AUTERIVE +33-6-07-63-80-64 (GSM)
FRANCE Email: ohp(at)pyrenet(dot)fr
------------------------------------------------------------------------------
Make your life a dream, make your dream a reality. (St Exupery)
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2009-02-20 13:48:12 | Re: WIP: hooking parser |
Previous Message | Peter Eisentraut | 2009-02-20 13:31:49 | Password prompting business |