Skip site navigation (1) Skip section navigation (2)

Re: Converting postgresql.conf parameters to kilobytes

From: Shridhar Daithankar <shridhar(at)frodo(dot)hserus(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Converting postgresql.conf parameters to kilobytes
Date: 2004-05-31 13:59:31
Message-ID: 200405311929.31680.shridhar@frodo.hserus.net (view raw, whole thread or download thread mbox)
Thread:
Lists: pgsql-hackers
On Monday 31 May 2004 18:41, Bruce Momjian wrote:
> 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?

The patch rounds it down owing to assignment of possible real number to 
integer.  but I didn't imagine of this requirement, to be honest. 

This seems to be better behavior than throwing an error.

 Shridhar

In response to

pgsql-hackers by date

Next:From: Darko PrenosilDate: 2004-05-31 15:34:18
Subject: Re: yet another contrib module
Previous:From: Pierre Emmanuel GrosDate: 2004-05-31 13:38:15
Subject: constraint upon view

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group