| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: psql patch |
| Date: | 2003-02-24 14:21:47 |
| Message-ID: | 2972.1046096507@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
"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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nigel J. Andrews | 2003-02-24 14:32:47 | Re: psql patch |
| Previous Message | Jeroen T. Vermeulen | 2003-02-24 10:09:32 | Re: psql patch |