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

From: Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>
To: PgSQL Performance ML <pgsql-performance(at)postgresql(dot)org>
Subject: Re: go for a script! / ex: PostgreSQL vs. MySQL
Date: 2003-10-11 10:43:27
Message-ID: 1065869007.24193.45.camel@haggis
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-performance

On Sat, 2003-10-11 at 05:22, Harald Fuchs wrote:
> In article <1065837333(dot)12875(dot)1(dot)camel(at)jester>,
> Rod Taylor <rbt(at)rbt(dot)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.

But it's too user-friendly to do it this way!

--
-----------------------------------------------------------------
Ron Johnson, Jr. ron(dot)l(dot)johnson(at)cox(dot)net
Jefferson, LA USA

When Swedes start committing terrorism, I'll become suspicious of
Scandanavians.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Network Administrator 2003-10-11 14:47:20 Re: Interfaces that support cursors
Previous Message Martijn van Oosterhout 2003-10-11 10:34:19 Re: log_duration and \timing times repeatably much higher than "Total runtime" from explain analyze

Browse pgsql-performance by date

  From Date Subject
Next Message Chris Faulkner 2003-10-11 11:12:01 Re: [SQL] sql performance and cache
Previous Message Richard Huxton 2003-10-11 10:39:10 Re: [SQL] sql performance and cache