| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Sean Chittenden <sean(at)chittenden(dot)org>, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql-server/ /configure /configure.in rc/incl ... |
| Date: | 2003-03-11 04:42:35 |
| Message-ID: | 1047357755.357.1.camel@tokyo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-performance |
On Mon, 2003-03-10 at 23:17, Christopher Kings-Lynne wrote:
> It would be nice to have this support there, however Tom was correct in
> saying it really only applies to network apps that are handling thousands of
> connections, all really, really fast. Postgres doesn't. I say you'd have
> to do the work, then do the benchmarking to see if it makes a difference.
... and if it doesn't make a significant difference, I'd oppose
including it in the mainline source. Performance optimization is one
thing; performance "optimization" that doesn't actually improve
performance is another :-)
Cheers,
Neil
--
Neil Conway <neilc(at)samurai(dot)com> || PGP Key ID: DB3C29FC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-03-11 04:53:01 | Re: pgsql-server/ /configure /configure.in rc/incl ... |
| Previous Message | Christopher Kings-Lynne | 2003-03-11 04:17:46 | Re: pgsql-server/ /configure /configure.in rc/incl ... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-03-11 04:53:01 | Re: pgsql-server/ /configure /configure.in rc/incl ... |
| Previous Message | Christopher Kings-Lynne | 2003-03-11 04:17:46 | Re: pgsql-server/ /configure /configure.in rc/incl ... |