Re: [HACKERS] Re: schema: pg_dump -s ipmeter (fwd)

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Sevo Stille <sevo(at)ip23(dot)net>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Re: schema: pg_dump -s ipmeter (fwd)
Date: 2000-02-15 17:23:42
Message-ID: Pine.BSF.4.21.0002151323120.74045-100000@thelab.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 15 Feb 2000, Peter Eisentraut wrote:

> On Mon, 14 Feb 2000, The Hermit Hacker wrote:
>
> > On Tue, 15 Feb 2000, Sevo Stille wrote:
> >
> > > The Hermit Hacker wrote:
> > > >
> > > > Good question ... I'm getting:
> > > >
> > > > pq_recvbuf: unexpected EOF on client connection
> > > >
> > > > from the backend, which *sounds* like psql is crashing ...
> > > >
> > > > gdb shows it dying:
> > > >
> > > > (gdb) where
> > > > #0 0x4814d0bc in strcmp () from /usr/lib/libc.so.3
> > > > #1 0x804fb28 in becomeUser ()
> > > > #2 0x804f268 in dumpIndices ()
> > > > #3 0x80501fa in dumpSchemaIdx ()
> > > > #4 0x804a8c2 in main ()
> > > > #5 0x80494dd in _start ()
>
> That looks more like a pg_dump trace to me. If you didn't know yet,
> pg_dump 7.0 can't be used with previous databases, so maybe that's a
> reason.

I *really* hope you don't mean that you cn't pg_dump from v6.5.3 (what I
was trying) and reload again into 7.0? :)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas 2000-02-15 17:26:20 Germany
Previous Message Lamar Owen 2000-02-15 16:48:06 Re: [HACKERS] Most Advanced