Re: [GENERAL] Critical Upgrade Instruction Bug?

From: phil(at)Stimpy(dot)netroedge(dot)com
To: Ed Loehr <eloehr(at)austin(dot)rr(dot)com>, pgsql-general(at)postgreSQL(dot)org
Subject: Re: [GENERAL] Critical Upgrade Instruction Bug?
Date: 2000-03-08 04:21:19
Message-ID: 20000307202119.O28761@Stimpy.netroedge.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Mar 07, 2000 at 10:04:22PM -0600, Ed Loehr wrote:
> phil(at)Stimpy(dot)netroedge(dot)com wrote:
> >
> > [...]
> > query buffer max length of 16384 exceeded
> > query line ignored
> > \smod
>
> IIRC, that usually happens when a string delimiter is missing. Maybe
> look for embedded apostrophes or something wonky with pgdump?
>
> Regards,
> Ed Loehr

I eventually got things working mostly with:

bash ./pg_dumpall -d -z > /tmp/dbnight.txt

At least this preserved permissions. I still had some tables
mysteriously be empty. So dumping those specific tables and
re-importing those seemed to do the trick. I'm hoping that this mess
is a result of bugs in the old version I was running (further
justifying the upgrade). I *think* I was running 6.3.0... my old
src/include/version.h said:

[...]
#define PG_RELEASE 6
#define PG_VERSION 3
#define PG_VERFILE "PG_VERSION"
[...]

This was prompted when a DB mysteriously corrupted it's self last
night after a year or so of use. (yikes!) But, I managed to dump it
and re-import it - saving most of the data, but I thought a better
permenent solution was to upgrade.

Anyways, things seems to work as they were, although a *LOT* faster
(about 5x?). :')

Thanks!

Phil

--
Philip Edelbrock -- IS Manager -- Edge Design, Corvallis, OR
phil(at)netroedge(dot)com -- http://www.netroedge.com/~phil
PGP F16: 01 D2 FD 01 B5 46 F4 F0 3A 8B 9D 7E 14 7F FB 7A

In response to

Browse pgsql-general by date

  From Date Subject
Next Message m.malicky 2000-03-08 10:30:28 Re: [GENERAL] 50 MB Table
Previous Message Ed Loehr 2000-03-08 04:04:22 Re: [GENERAL] Critical Upgrade Instruction Bug?