| From: | Dave Crooke <dcrooke(at)gmail(dot)com> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Paul McGarry <paul(at)paulmcgarry(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: shared_buffers advice |
| Date: | 2010-05-28 21:14:18 |
| Message-ID: | AANLkTimvyRfRY2TT9WV18VlC3rUKYj_2iKYWBGneHc1Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
If, like me, you came from the Oracle world, you may be tempted to throw a
ton of RAM at this. Don't. PG does not like it.
On Fri, May 28, 2010 at 4:11 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>wrote:
> On Mon, May 24, 2010 at 12:25 PM, Merlin Moncure <mmoncure(at)gmail(dot)com>
> wrote:
> > *) shared_buffers is one of the _least_ important performance settings
> > in postgresql.conf
>
> Yes, and no. It's usually REALLY helpful to make sure it's more than
> 8 or 24Megs. But it doesn't generally need to be huge to make a
> difference.
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2010-05-28 21:16:01 | Re: shared_buffers advice |
| Previous Message | Scott Marlowe | 2010-05-28 21:11:15 | Re: shared_buffers advice |