Re: Trouble getting effective_cache_size parameter to take - Mailing list pgsql-general

From Hardwick, Joe
Subject Re: Trouble getting effective_cache_size parameter to take
Date
Msg-id 1D134C5F69F974449CCE35EFBA14205B020F3FF5@CMBFISLTC01.FNFIS.COM
Whole thread Raw
In response to Re: Trouble getting effective_cache_size parameter to take  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Turns out someone had placed a second line further down in the file I
didn't realize was there... So it set it, then reset it.

Thanks,
Joe

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Tuesday, April 08, 2008 8:53 AM
To: Hardwick, Joe
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Trouble getting effective_cache_size parameter to
take

"Hardwick, Joe" <Joe.Hardwick@fnis.com> writes:
> I've got a Postgres v8.2.4 server that we recently upped from 2GB RAM
> to 6GB.  I added:

> effective_cache_size = 5120MB

> to the postgresql.conf file but when I restart the server and do a
> "show all" it always comes back with "1000MB".  I can set it manually
> and it takes but for some reason it just seems to ignore it in the
config file.

Sure sounds to me like you're editing the wrong config file ...

            regards, tom lane

______________

The information contained in this message is proprietary and/or confidential. If you are not the
intended recipient, please: (i) delete the message and all copies; (ii) do not disclose,
distribute or use the message in any manner; and (iii) notify the sender immediately. In addition,
please be aware that any message addressed to our domain is subject to archiving and review by
persons other than the intended recipient. Thank you.
_____________

pgsql-general by date:

Previous
From: "Hardwick, Joe"
Date:
Subject: Crash after VACUUM FULL cancel
Next
From: Syra.Didelez@agfa.com
Date:
Subject: Re: Problem with windows Postgres 8.3.1 MSI binary distribution