| From: | Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> |
|---|---|
| To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
| 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 12:24:49 |
| Message-ID: | Pine.GSO.4.02A.10002151323220.28210-100000@Krokodil.DoCS.UU.SE |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Peter Eisentraut Sernanders vaeg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sevo Stille | 2000-02-15 12:58:02 | Re: [HACKERS] Re: schema: pg_dump -s ipmeter (fwd) |
| Previous Message | Michael Meskes | 2000-02-15 12:24:06 | Re: [HACKERS] function defined in libpq? |