| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | James Mansion <james(at)mansionfamily(dot)plus(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgkill |
| Date: | 2008-03-31 20:02:03 |
| Message-ID: | 19521.1206993723@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
James Mansion <james(at)mansionfamily(dot)plus(dot)com> writes:
> I was looking at the notify processing in async.c and I noticed that
> kill is called whether or not the
> process has been signalled already, and whether or not 'this' process
> has signalled the process.
> It seems unecessary to me -
It's not that easy to be sure of either of those conditions.
The notify code needs to be dumped and rewritten from scratch
--- I see little point in marginal optimizations, and none at
all in doing anything while the pg_listener table is still used
as communication mechanism.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2008-03-31 20:07:57 | Re: POSIX shared memory support |
| Previous Message | Stephen Frost | 2008-03-31 19:55:06 | Re: actualized SQL/PSM patch |