From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Sean Chittenden <sean(at)chittenden(dot)org> |
Cc: | Kris Jurka <books(at)ejurka(dot)com>, "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Urgent: 10K or more connections |
Date: | 2003-07-20 03:56:20 |
Message-ID: | 18351.1058673380@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Sean Chittenden <sean(at)chittenden(dot)org> writes:
> No where, everything remains as is. I actually think you'll
> appreciate the simplicity of this once I'm done explaining how I'm
> going about this.
I don't think you heard a word I said :-(
You appear to be adding a whole lot of platform dependency (passing
FDs around other than by fork() is not portable) in return for loss
of functionality (applications can't rely on session state anymore)
and highly dubious performance gain (just because a backend has started
does not mean it's built up a reasonable working set of cache entries;
you can't expect that firing off a new backend for every transaction
is going to be anything but a huge performance loss, even if you assume
its visible session state is exactly what the application needs).
Also it sounds to me like the postmaster will now become a performance
bottleneck, since it will need to be involved in every transaction start.
You're welcome to pursue this if you like, but I'll bet lunch that
you are wasting your time.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-07-20 04:59:47 | Re: Error Message Using pg_dumpall |
Previous Message | Bruce Momjian | 2003-07-20 01:22:28 | Re: Inherits tables and current CVS |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-07-20 04:00:57 | Re: [HACKERS] allowed user/db variables |
Previous Message | Tom Lane | 2003-07-20 03:19:59 | Re: [HACKERS] allowed user/db variables |