From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Chris Bitmead <chris(dot)bitmead(at)bigfoot(dot)com> |
Cc: | pgsql-general(at)hub(dot)org |
Subject: | Re: [GENERAL] Upgrading from 6.3->6.4.2/6.5b1 possible |
Date: | 1999-05-31 00:25:47 |
Message-ID: | 199905310025.UAA15288@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>
> I've seen this problem too in 6.5 beta. I don't have a solution, but I'd
> just like to add my voice to say that this problem is real.
>
> Actually, I did have a kind of solution. If you dump proper insert
> statements into the dump and then run every insert in a separate
> process. Ugly but workable if the number isn't too great.
>
> while read A
> do
> echo "$A" | psql databasename
> done <dumpfilename
>
>
We don't hear about this very often. Can someone tell us exactly what a
bad load looks like, or a cause.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Heflin | 1999-05-31 01:33:25 | Re: [GENERAL] Upgrading from 6.3->6.4.2/6.5b1 possible |
Previous Message | Michael A. Koerber SR | 1999-05-31 00:07:11 | Re: [GENERAL] Upgrading from 6.3->6.4.2/6.5b1 possible |