Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] Upgrading from 6.3->6.4.2/6.5b1 possible

From: Chris Bitmead <chris(dot)bitmead(at)bigfoot(dot)com>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-general(at)hub(dot)org
Subject: Re: [GENERAL] Upgrading from 6.3->6.4.2/6.5b1 possible
Date: 1999-05-31 02:11:06
Message-ID: 3751EFBA.4B3DE5D@bigfoot.com (view raw or flat)
Thread:
Lists: pgsql-general
Bruce,
I've put up a script for ftp that shows some wierd behaviour. This
script was created by hand, so it's possible that some errors are caused
by syntax errors (although I spent a while trying to find them without
success).

I think the point is that it is not recovering from/ reporting the error
well (if there is one that is). It just gives errors about "max query
size exceeded". Something happens part way through, and then you just
get the same error thousands of times.

ftp://tech.com.au/pub/load-error.gz


Bruce Momjian wrote:
> 
> >
> > 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

In response to

Responses

pgsql-general by date

Next:From: HowieDate: 1999-05-31 03:35:40
Subject: bug in 6.4.2?
Previous:From: Kevin HeflinDate: 1999-05-31 01:33:25
Subject: Re: [GENERAL] Upgrading from 6.3->6.4.2/6.5b1 possible

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group