| From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: postgres wish list |
| Date: | 2009-02-19 10:14:04 |
| Message-ID: | gnjbdc$u32$1@ger.gmane.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Sameer Mahajan, 19.02.2009 07:38:
> * Shared memory based connectivity: As such postgres has client
> - server model. The TCP-IP nature of its connectivity further adds to
> the latency of this communication. It will be nice to have a shared
> memory based connectivity between libpq front end and the back end.
I have never worked with an application that ran on the same server as the database.
Application server (e.g. for webapps) and database server are almost always on different machines (even more so for client/server applications).
So an application in production system doesn't really benefit from this. It will always have to go through tcp.
Or am I missing something?
Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Katson | 2009-02-19 10:36:35 | Accessing array elements in a FOR PL/pgsql loop |
| Previous Message | Mike Christensen | 2009-02-19 10:11:50 | Re: When adding millions of rows at once, getting out of disk space errors |