Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.8.8/8.7.5) with ESMTP id AAA08119; Fri, 22 May 1998 00:37:32 -0400 (EDT) Received: (from maillist@localhost) by candle.pha.pa.us (8.8.5/8.8.5) id AAA19514; Fri, 22 May 1998 00:36:32 -0400 (EDT) From: Bruce Momjian Message-Id: <199805220436.AAA19514@candle.pha.pa.us> Subject: Re: [HACKERS] Time to fix libpgtcl for async NOTIFY To: tgl@sss.pgh.pa.us (Tom Lane) Date: Fri, 22 May 1998 00:36:32 -0400 (EDT) Cc: pgsql-hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org In-Reply-To: <23936.895792415@sss.pgh.pa.us> from "Tom Lane" at May 21, 98 07:13:35 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > There's some risk of breaking existing applications, since the apps > might not be prepared for pg_listen callbacks occurring except at the > specific time they execute pg_notifies. But that doesn't seem really > likely to be a problem. Besides, since both these commands are > undocumented, I imagine not very many libpgtcl applications use them. > (A quick search of the archives turned up only a message from Massimo > Dal Zotto about this topic, and he seemed to agree that getting rid of > pg_notifies would be better.) > > Any comments? Yep, get rid of the old stuff. I am sure people didn't use it because of the performance problem. Your cleanup will make it use-able. -- Bruce Momjian | 830 Blythe Avenue maillist@candle.pha.pa.us | Drexel Hill, Pennsylvania 19026 + If your life is a hard drive, | (610) 353-9879(w) + Christ can be your backup. | (610) 853-3000(h)