From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Mitch Vincent" <mitch(at)venux(dot)net> |
Cc: | "Postgres Hackers List" <hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] plpgsql problem.. |
Date: | 2000-02-02 04:09:37 |
Message-ID: | 16942.949464577@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Mitch Vincent" <mitch(at)venux(dot)net> writes:
> Ok guys, brand new problem!
> Now the backend segfaults.
> StartTransactionCommand
> query: select * from invoice where invoice_number=1
> ProcessQuery
> CommitTransactionCommand
> pq_recvbuf: unexpected EOF on client connection
> proc_exit(0) [#0]
> shmem_exit(0) [#0]
> exit(0)
> /usr/local/pgsql/bin/postmaster: reaping dead processes...
> /usr/local/pgsql/bin/postmaster: CleanupProc: pid 75928 exited with status 0
> I get that in the log file.... Can anyone see anything that might point to
> the reason behind the segfault?
Um, I see no backend segfault there --- I see a backend exiting in a
perfectly orderly fashion after detecting that the client closed the
channel. The client didn't send the expected "quit" (X) message,
which might or might not be normal behavior for that client. But if
you've got a backend segfault problem, this doesn't document it...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Don Baccus | 2000-02-02 05:34:17 | Re: [HACKERS] RE: cvs-commit-digest V1 #856 |
Previous Message | Tom Lane | 2000-02-02 03:52:56 | Re: [HACKERS] RE: cvs-commit-digest V1 #856 |