| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org, Michael Fuhr <mike(at)fuhr(dot)org> |
| Subject: | Re: SOLVED: unexpected EIDRM on Linux |
| Date: | 2007-07-02 20:40:11 |
| Message-ID: | 22467.1183408811@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> I'm going to generate a smaller test program showing this and file
> a bug report at Red Hat.
Filed as
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=246509
in case anyone wants to track it. (I suspect the Red Hat kernel guys
will just bounce it upstream, but that's their call not mine.)
> In the mean time, it looks like we should assume EIDRM means EINVAL
> on Linux, because AFAICS there is not actually anyplace in that code
> that should return EIDRM; their data structure doesn't really have
> any state that would justify returning such a code.
Patch for this committed in all active branches.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2007-07-02 20:45:14 | Re: [COMMITTERS] pgsql: Fix failure to restart Postgres when Linux kernel returns EIDRM |
| Previous Message | Tom Lane | 2007-07-02 20:12:27 | pgsql: Fix failure to restart Postgres when Linux kernel returns EIDRM |