From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [Pgbuildfarm-members] guppie: 64MB RAM too small? |
Date: | 2006-03-21 14:40:20 |
Message-ID: | 44201054.6090402@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | buildfarm-members pgsql-hackers |
Jim C. Nasby wrote:
>Adding -hackers.
>
>
[removing -buildfarm :-) ]
>Ok, lets go back to my original point then: initdb should be made to
>check that you can actually open as many connections as it's trying to
>set max_connections to. If it can't, it should drop max_connections down
>(and possibly add a note to postgresql.conf indicating that it did so).
>
>
At the time it sets max_connections there is no server to test against.
initdb in fact never uses a standard client connection at all, and never
starts postmaster. To do a check on max_connections you would have to
start postmaster and then try to start that many client connections.
That's a lot of extra lifting to put into initdb for what is arguably at
worst a rare problem.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-03-21 14:48:40 | Re: [Pgbuildfarm-members] guppie: 64MB RAM too small? |
Previous Message | Jim C. Nasby | 2006-03-21 14:19:15 | Re: [Pgbuildfarm-members] guppie: 64MB RAM too small? |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-03-21 14:48:40 | Re: [Pgbuildfarm-members] guppie: 64MB RAM too small? |
Previous Message | Martijn van Oosterhout | 2006-03-21 14:27:10 | Re: [GENERAL] A real currency type |