Re: go for a script! / ex: PostgreSQL vs. MySQL

In article <1065837333.12875.1.camel@jester>,
Rod Taylor <rbt@rbt.ca> writes:

>> Would anyone object to a patch that exports the blocksize via a
>> readonly GUC?  Too many tunables are page dependant, which is
>> infuriating when copying configs from DB to DB.  I wish pgsql had some
>> notion of percentages for values that end with a '%'.

> Rather than showing the block size, how about we change the tunables to
> be physical sizes rather than block based?

>         effective_cache_size = 1.5GB
>         shared_buffers = 25MB

Amen!  Being forced to set config values in some obscure units rather
than bytes is an ugly braindamage which should be easy to fix.