Re: "--tuning" compile and runtime option (?)

From: "Rod Taylor" <rbt(at)barchord(dot)com>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "Hackers List" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "--tuning" compile and runtime option (?)
Date: 2001-04-09 04:22:20
Message-ID: 00de01c0c0ac$ab5bc540$1600a8c0@jester
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I like this. Ensure that tips can be dumped into a log file --
preferably separate from the main one -- so it can be run on a live
system for a short period of time, recorded then analyzed later.
--
Rod Taylor

There are always four sides to every story: your side, their side, the
truth, and what really happened.
----- Original Message -----
From: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: "Justin Clift" <jclift(at)iprimus(dot)com(dot)au>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Sent: Monday, April 09, 2001 12:18 AM
Subject: Re: [HACKERS] "--tuning" compile and runtime option (?)

> My idea was to have PostgreSQL output tips to help performance. The
> TODO item is:
>
> * Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
> ANALYZE, and CLUSTER
>
> I also will be writing an article on performance tuning this month.
> What parameters would these options you suggest control? I usually
> prefer options that have more concrete effect.
>
>
> > Just thinking about the future directions PostgreSQL is taking,
and it
> > seems (just a feeling) like most people prefer it to be as self
tuning
> > as possible.
> >
> > In trying to think about how it will/would do that I think
PostgreSQL
> > will need to know "how much" of the resources of the server its
on, it's
> > allowed to take.
> >
> > Can think of three scenario's, 1) Single-purpose PostgreSQL server
2)
> > shared function server (i.e. Apache, Postgres, etc on the same
box) 3)
> > Embedded or otherwise resource limited server (Palmtop, etc).
> >
> > When we get around to PostgreSQL's self-tuning ability being
actively
> > developed (and I think Bruce has done some of the very start with
his
> > monitor program), perhaps having a compile time option to set the
> > default for the server, and a runtime option in case it changes?
> >
> > i.e.
> >
> > --tuning=superserver
> > --tuning=shared
> > --tuning=embedded
> >
> > postmaster -t superserver
> > postmaster -t shared
> > postmaster -t embedded
> >
> > What do people think?
> >
> > Regards and best wishes,
> >
> > Justin Clift
> >
> > P.S. - I'm not on the Hackers mailing list from this account. Can
> > anyone responding please include me directly in their replies?
> >
> > --
> > "My grandfather once told me that there are two kinds of people:
those
> > who work and those who take the credit. He told me to try to be in
the
> > first group; there was less competition there."
> > - Indira Gandhi
> >
> > ---------------------------(end of
broadcast)---------------------------
> > TIP 2: you can get off all lists at once with the unregister
command
> > (send "unregister YourEmailAddressHere" to
majordomo(at)postgresql(dot)org)
> >
>
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania
19026
>
> ---------------------------(end of
broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://www.postgresql.org/search.mpl
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-04-09 04:32:58 Re: "--tuning" compile and runtime option (?)
Previous Message Bruce Momjian 2001-04-09 04:18:32 Re: "--tuning" compile and runtime option (?)