Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: pgkill
- 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: Mon, 31 Mar 2008 16:02:03 -0400
- Message-id: <19521.1206993723@sss.pgh.pa.us> <text/plain>
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
- References:
- pgkill
- From: James Mansion
- pgkill
- Prev by Date: Re: actualized SQL/PSM patch
- Next by Date: Re: POSIX shared memory support
- Previous by thread: pgkill
- Next by thread: Re: pgkill
- Indexes: