From: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl>, Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: psql patch |
Date: | 2003-02-24 14:32:47 |
Message-ID: | Pine.LNX.4.21.0302241428400.8354-100000@ponder.fairway2k.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
On Mon, 24 Feb 2003, Tom Lane wrote:
> "Jeroen T. Vermeulen" <jtv(at)xs4all(dot)nl> writes:
> > Imagine you're maintaing a program that sends out notifications, and
> > you want to get a feel for when this happens. I think it would be
> > nice to be able to open a shell, run psql, issue a LISTEN and just
> > let it sit there and print out anything that comes along, while you
> > play with the application in another window.
>
> I'd be happier with it if there were a switch that enabled this behavior
> (and it were *not* on by default). That would eliminate one of the
> things that was bothering me, which was the prospect of every psql
> everywhere consuming cycles to check for notifications. If you did that
> it would likely also be acceptable to print notifications in the midst
> of type-in.
>
Wouldn't it make sense to have a separate utility for this? Something like
pg_listen? Configuration of the conditions could simply be by command line
switches ( or even just pg_listen <condition> [<condition> ...] ). Perhaps it's
a gborg or contrib utility rather than core though.
--
Nigel J. Andrews
From | Date | Subject | |
---|---|---|---|
Next Message | Karel Zak | 2003-02-24 16:40:34 | to_char PL/MI fix |
Previous Message | Tom Lane | 2003-02-24 14:21:47 | Re: psql patch |