| From: | Dirk Lutzebaeck <lutzeb(at)aeccom(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Backend crashes in 7.0.3 |
| Date: | 2000-12-27 09:54:13 |
| Message-ID: | 14921.48197.239445.904078@ampato.core.aeccom.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Tom Lane writes:
> Dirk Lutzebaeck <lutzeb(at)aeccom(dot)com> writes:
> > It may be that there is some kernel corruption appearing here. I'm
> > using kernel nfs on Linux 2.2.10 with a Solaris8 i86pc client. I saw
> > some weird NFS error messages on the Linux system which are related to
> > the solaris client. I suspect the kernel nfs daemon corrupting memory
> > areas where postgres shared mem resides. I'm currently trying to dig more into
> > the problem. Could this be possible?
>
> Seems like a bizarre theory. In particular, why would 7.0.3 be affected
> and not 7.0.2?
Sorry, it seems I was on the wrong track. It has nothing do to with
NFS, I just panicked... I'm currently looking into ApacheDBI a modperl
utility to reuse open db connections. In any case the backend messages
are odd. It seems I misunderstand ApacheDBI loosing a DB connection
with a backend crash.
Dirk
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgsql-bugs | 2000-12-27 10:48:42 | pg_toast_xxx table's file leak (grows indefinitely) |
| Previous Message | Tom Lane | 2000-12-25 17:47:11 | Re: [BUGS] postgres bombs for continous selects.... |