Re: Converting postgresql.conf parameters to kilobytes

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: shridhar(at)frodo(dot)hserus(dot)net
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Converting postgresql.conf parameters to kilobytes
Date: 2004-05-31 13:11:42
Message-ID: 200405311311.i4VDBgR07545@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Shridhar Daithankar wrote:
> On Sunday 30 May 2004 21:33, Tom Lane wrote:
> > Shridhar Daithankar <shridhar(at)frodo(dot)hserus(dot)net> writes:
> > > I was toying around with idea of converting all the memory related
> > > parameters in postgresql.conf to kilobytes for simplicity and
> > > uniformity.
> >
> > Why is that a good idea?
>
> Right now following are measured in pages
> wal_buffers
> shared_buffers
> effective_cachesize
>
> Following are in kbs
> work_mem
> maintenance_work_mem
> max_stack_depth
>
> while rest of the memory parameters are in kb. I thought being uniform would
> be good. Besides it will make it independent of page size as well.

Sounds good to me. How are you handling cases where the value has to be
a multiple of page size --- rounding or throwing an error?

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2004-05-31 13:12:10 Re: Nested xacts: looking for testers and review
Previous Message Jan Wieck 2004-05-31 13:01:39 Re: pg_dump --comment?