| From: | klo uo <klonuo(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: question about memory usage |
| Date: | 2014-07-23 13:56:22 |
| Message-ID: | CAA-8Ld8Q3_40jLR-ZNnxXGyBtgRZiTS2MEkXO_bwVgdRSR47bg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bill, thanks for your reply.
"shared_buffers" is set to "128MB".
Now that you mention config file, the only thing I did change there, and
was suggested to me while I made some on my databases was
"max_locks_per_transaction = 50000" (which has default value 10000).
After resetting "max_locks_per_transaction" to default value and restarting
the server, memory occupied in working set reduced linearly to around 200
MB.
I guess this is it.
On Wed, Jul 23, 2014 at 5:53 AM, Bill Moran <wmoran(at)potentialtech(dot)com>
wrote:
>
> I'm not an expert on the Windows version, so I could be off-base, but the
> POSIX versions of Postgres allocate shared_buffers worth of memory at
> startup
> and lock it for exclusive use by Postgres. Do you have shared_buffers set
> to
> around 1G, perhaps?
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2014-07-23 14:09:43 | Re: |
| Previous Message | Rebecca Clarke | 2014-07-23 09:45:56 | Index usage with slow query |