Re: GUC with units, details - Mailing list pgsql-hackers

From Michael Glaesemann
Subject Re: GUC with units, details
Date
Msg-id 61811CA7-4DCE-406B-845D-05BFF42B39FE@seespotcode.net
Whole thread Raw
In response to Re: GUC with units, details  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Jul 27, 2006, at 14:03 , Tom Lane wrote:

> What we're talking about here is ways to specify the intended
> usage with other units (eg "I want N megabytes of shared buffers") but
> that's not going to magically let you allocate half a shared buffer.
> Peter's not said exactly how he plans to deal with this, but I suppose
> it'll round off one way or the other ...

Thanks, Tom. That make sense to me, and helps me better understand  
the motivation for the patch. I was a bit thrown off by comments such  
as this one by Peter [1]:

> I'd imagine that one of the first things someone will want to try is
> something like SET work_mem TO '10MB', which will fail or misbehave
> because 10000000 bytes do not divide up into chunks of 1024 bytes.   
> Who
> wants to explain to users that they have to write '10MiB'?

Granted, the K=1024/1000 issue will affect how 10MB is interpreted,  
but if it's rounded to the nearest whole page or buffer, it shouldn't  
"fail or misbehave", I'd think.

Michael Glaesemann
grzm seespotcode net

[1](http://archives.postgresql.org/pgsql-hackers/2006-07/msg01249.php)



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: On-disk bitmap index patch
Next
From: Peter Eisentraut
Date:
Subject: Re: GUC with units, details