From: Bruce Momjian <maillist@candle.pha.pa.us>
To: tgl@sss.pgh.pa.us
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [HACKERS] Time to fix libpgtcl for async NOTIFY
Date: Fri, 22 May 1998 00:36:32 -0400 (EDT)
Message-ID: <199805220436.AAA19514@candle.pha.pa.us> (raw)
In-Reply-To: <23936.895792415@sss.pgh.pa.us>
> 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)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: maillist@candle.pha.pa.us, tgl@sss.pgh.pa.us, pgsql-hackers@postgreSQL.org
Subject: Re: [HACKERS] Time to fix libpgtcl for async NOTIFY
In-Reply-To: <199805220436.AAA19514@candle.pha.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox