I've been trying to work out a reliable script to determine,
after pg_ctl start, that the server is done attempting
to come up, and that it has either succeeded OR FAILED.
This is for several hundred unattended appliance-type servers,
currently on PG 8.0 but soon to be on 8.3
Haven't found anythi
Only kernel.shmmax have
importance in this case?
about kernel.shmmax it has configured not by me.
De: Richard Huxton <[EMAIL PROTECTED]>
Para: paulo matadr <[EMAIL PROTECTED]>
Cc: GENERAL <[EMAIL PROTECTED]>; admin
Enviadas: Quarta-feira, 12 de Novembro de 20
paulo matadr wrote:
> I need help to alter max_connections em my database, this parameter
> stay in defalt MAX_CONNECTIONS=100
> I want to change for MAX_CONNECTIONS=300. about parameters below,
> need to change anything?
>
> 1 -sysctl.conf
>
> kernel.shmmax = 68719476736
> kernel.shmall = 429496
I need help to alter max_connections em my database, this parameter stay in
defalt MAX_CONNECTIONS=100
I want to change for MAX_CONNECTIONS=300.
about parameters below, need to change anything?
1 -sysctl.conf
kernel.shmmax = 68719476736
kernel.shmall = 4294967296
# - Memory -
2-Postgresql.conf
On Wed, 2008-11-12 at 16:10 +0200, Julius Tuskenis wrote:
> Hello, list.
>
> I have one simple SQL function returning result set that takes around 3
> seconds to execute. But if I execute the Select it executes directly -
> it takes only around 30 ms. Why so big difference?
Probably caching the
Hello, list.
I have one simple SQL function returning result set that takes around 3
seconds to execute. But if I execute the Select it executes directly -
it takes only around 30 ms. Why so big difference? What should I check?
I must also say, that this started this afternoon.
PG: 8.3.3
OS:
