Anj Adu writes:
> For a 64 bit machine..does the higher shared buffer setting really
> offer a significant improvement over a 32 bit lower setting coupled
> with linux caching ? Is the postgres shared buffer algorithm superior
> to the linux caching algorithm to favor a switch to 64 bit
There are
For a 64 bit machine..does the higher shared buffer setting really
offer a significant improvement over a 32 bit lower setting coupled
with linux caching ? Is the postgres shared buffer algorithm superior
to the linux caching algorithm to favor a switch to 64 bit
On Fri, Sep 11, 2009 at 9:50 AM,
Tom Lane a écrit :
Nicolas Michel writes:
- I have 16Go of RAM on that server (but 32bits OS with bigmem kernel ;
so I set shared buffer to 35 (~2,7GB) for a shmmax of 40
(~3,8GB)
On a 32-bit machine that's just insane. You've got something like 300MB
left over in the process ad
Nicolas Michel writes:
> - I have 16Go of RAM on that server (but 32bits OS with bigmem kernel ;
> so I set shared buffer to 35 (~2,7GB) for a shmmax of 40
> (~3,8GB)
On a 32-bit machine that's just insane. You've got something like 300MB
left over in the process address space (ass
Lewis Kapell a écrit :
I think you've missed Tom's point. You need to set maintenance_work_mem
based on the physical capacity of your system. If it (the parameter) is
set too high, your operating system will encounter errors when trying to
satisfy the requests that Postgres is making.
Also
Sent: Friday, September 11, 2009 10:37 AM
To: Tom Lane
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Vacuum analyse after a long time without one ...
Tom Lane a écrit :
> Nicolas Michel writes:
>> I have a problem with a database. The last full vacuum analyse was made
>> long t
I think you've missed Tom's point. You need to set maintenance_work_mem
based on the physical capacity of your system. If it (the parameter) is
set too high, your operating system will encounter errors when trying to
satisfy the requests that Postgres is making.
Also as Tom just pointed out,
Nicolas Michel writes:
> Tom Lane a écrit :
>> What is your maintenance_work_mem setting? It rather looks like it's
>> more than your system will really allow.
> I already tried to set the work_mem setting to the max value I can but
> it changed nothing.
I did not say work_mem, and increasing
Tom Lane a écrit :
Nicolas Michel writes:
I have a problem with a database. The last full vacuum analyse was made
long time ago... So I tried to start launching a vacuum analyse and I
get this error :
$ vacuumdb -az
vacuumdb: vacuuming database "postgres"
VACUUM
vacuumdb: vacuuming database
Nicolas Michel writes:
> I have a problem with a database. The last full vacuum analyse was made
> long time ago... So I tried to start launching a vacuum analyse and I
> get this error :
> $ vacuumdb -az
> vacuumdb: vacuuming database "postgres"
> VACUUM
> vacuumdb: vacuuming database "mexi"
> v
I have a problem with a database. The last full vacuum analyse was made
long time ago... So I tried to start launching a vacuum analyse and I
get this error :
$ vacuumdb -az
vacuumdb: vacuuming database "postgres"
VACUUM
vacuumdb: vacuuming database "mexi"
vacuumdb: vacuuming of database "mexi" f
11 matches
Mail list logo
