| 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 18:35:15 |
| Message-ID: | 4659.1046111715@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:
> However I just took a look at the docs for readline and apparently it
> was designed with select() in mind. So it should be possible to
> implement this without any cost to scalability: the server doesn't
> care if the frontend is listening when it sends out the notification,
> and the frontend can sleep until either a notification or a keypress
> arrives.
Cool; if you can do it that way then the wasted-cycles objection is
gone. (I don't think it would have been very interesting to implement
the functionality only in the no-readline case, 'cuz just about everyone
seems to use readline builds.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-02-24 19:16:07 | Re: to_char PL/MI fix |
| Previous Message | Manfred Spraul | 2003-02-24 18:24:09 | performance: use pread instead of lseek+read |