| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | prlw1(at)cam(dot)ac(dot)uk |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Another nasty cache problem |
| Date: | 2000-02-04 20:58:57 |
| Message-ID: | 4803.949697937@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> writes:
> newnham=# select crsids.surname, "tblPerson"."Surname" from crsids,"tblPerson" where crsids.usn="tblPerson"."USN"::int4;
> pqReadData() -- backend closed the channel unexpectedly.
> This probably means the backend terminated abnormally
> before or while processing the request.
> The connection to the server was lost. Attempting reset: Failed.
> Any thoughts on where to look?
Is there anything in the postmaster log? Is there a core file (look
in the database subdirectory, ie .../data/base/yourdatabase/core)?
If so, compiling the backend with -g and extracting a backtrace from
the resulting corefile with gdb would be very useful info.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Assaf Arkin | 2000-02-04 21:48:38 | Identifying duplicate key inserts |
| Previous Message | Michael Meskes | 2000-02-04 19:45:48 | Re: [HACKERS] Two backends at the same time |