pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
To: pgsql-patches@postgresql.org
Subject: Re: Another POC initdb patch
Date: Mon, 7 Jul 2003 12:15:59 +0530
Message-ID: <200307071215.59227.shridhar_daithankar@nospam.persistent.co.in> (raw)
In-Reply-To: <9957.1057505128@sss.pgh.pa.us>
References: <200307061940.32831.shridhar_daithankar@nospam.persistent.co.in>
	<9957.1057505128@sss.pgh.pa.us>

On Sunday 06 July 2003 20:55, Tom Lane wrote:
> Shridhar Daithankar <shridhar_daithankar@persistent.co.in> writes:
> > In addition to Tom's patch, this patch asks tuning parameters right away,
> > while doing initdb.
>
> Sorry, there is zero chance of putting any interactivity into initdb.
> Most RPM installations run it from the RPM install script and would be
> unable to cope with this.

Hmm.. If distro. vendors can put a wrapper of service script around it on 
their own, how much difficult it is to modify initdb to revert back to 
original behaviour?

I think it would be fair on linux distro. vendors part if they decide to put a 
reasonable default for shared_buffers. Unlike postgresql community, they 
don't haev to worry about OS protability because they know that it is going 
to run on only linux.

I mailed mandrake long time back, requesting a config file for service script 
where it would allow to specify database location. No reply.

> I disagree with the concept of expecting someone to supply useful values
> at install time anyway, since a newbie is the *least* likely to have any
> idea what to say at that time.  Heck, the experts can hardly agree on
> what to use ...

Whatever user says might not be the best or optimum but will be likely to be 
much better than 64.

I agree that this is not part of rpm philosophy. Install and configure is only 
followed by debian IIRC.

Furthermore this could take care of user complains that postgresql does not 
have reasonable defaults. Problems with such approach w.r.t. linux distro.s 
aren't exactly impossible to solve. May be we could add it to release notes, 
for their convinience.

Another proposal is to take out everything interactive I put it in patch, 
write another shell script, that would tune postgresql.conf, like the 
configuration wizard you suggested.

No matter where it goes, users would be very happy to have a tool which hand 
holds them to a reasonanly working config file and points to right 
documentation thereafter.

 Shridhar




view thread (3+ messages)

Message-ID: <200307071215.59227.shridhar_daithankar@nospam.persistent.co.in>
Permalink:  ../200307071215.59227.shridhar_daithankar@nospam.persistent.co.in/
Also on:    postgresql.org/message-id/200307071215.59227.shridhar_daithankar@nospam.persistent.co.in

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: shridhar_daithankar@persistent.co.in, pgsql-patches@postgresql.org
  Subject: Re: Another POC initdb patch
  In-Reply-To: <200307071215.59227.shridhar_daithankar@nospam.persistent.co.in>
  References: <200307061940.32831.shridhar_daithankar@nospam.persistent.co.in> <9957.1057505128@sss.pgh.pa.us> <200307071215.59227.shridhar_daithankar@nospam.persistent.co.in>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox