Michael Coffman <[EMAIL PROTECTED]> writes:
> Whenever I start postmaster w/ greater than 64 buffers, I get the following
> message:
> Starting postgresql service: 010307.17:10:34.877 [1631] IpcMemoryCreate:
> shmget failed (Invalid argument) key=5432001, size=2703360, permission=600
Perhaps th
Whenever I start postmaster w/ greater than 64 buffers, I get the following
message:
Starting postgresql service: 010307.17:10:34.877 [1631] IpcMemoryCreate:
shmget failed (Invalid argument) key=5432001, size=2703360, permission=600
This type of error is usually caused by an improper
shared memo
Colleen Williams <[EMAIL PROTECTED]> writes:
> 3. after stopping and restarting postgresql (postmaster) again the disk
> usage is back to 56%
Oh? Stopping and restarting the postmaster shouldn't make any
difference as far as postgres itself is concerned. May I ask what
you are doing with the p
[EMAIL PROTECTED] writes:
>William L James writes:
>
>> script - su -l postgresql -c "/usr/bin/pg_ctl -D $PGDATA -p
>> /usr/bin/postmaster start >>/var/log/postgresql 2>&1"), but
>> when the weekly logrotate.d function kicks in, Postgres logging
>> stops.
>
>The logging probably continues to go to
Hi
We are experiencing this scenario -
1. at the point postgresql (postmaster) is stopped and restarted the disk
usage was 56% (277336 blocks)
2. after about 2 days the disk usage is 69% (339528 blocks)... after about
1 week it goes up to 100%
3. after stopping and restarting postgresql (postmas
