Re: Solaris initdb fails: shmmax tweak alternative?

Поиск
Список
Период
Сортировка
Искать
От
Robert Treat
Тема
Re: Solaris initdb fails: shmmax tweak alternative?
Дата
Msg-id
1081259949.31791.25.camel@camel
Ответ на
Список
Дерево обсуждения
Solaris initdb fails: shmmax tweak alternative? "Greg Sabino Mullane" <greg@turnstep.com>
Re: Solaris initdb fails: shmmax tweak alternative? Andrew Sullivan <ajs@crankycanuck.ca>
Re: Solaris initdb fails: shmmax tweak alternative? Tom Lane <tgl@sss.pgh.pa.us>
Re: Solaris initdb fails: shmmax tweak alternative? "Greg Sabino Mullane" <greg@turnstep.com>
Re: Solaris initdb fails: shmmax tweak alternative? Tom Lane <tgl@sss.pgh.pa.us>
Re: Solaris initdb fails: shmmax tweak alternative? "Greg Sabino Mullane" <greg@turnstep.com>
Re: Solaris initdb fails: shmmax tweak alternative? "Andrew Dunstan" <andrew@dunslane.net>
Re: Solaris initdb fails: shmmax tweak alternative? Robert Treat <xzilla@users.sourceforge.net>
Re: Solaris initdb fails: shmmax tweak alternative? Tom Lane <tgl@sss.pgh.pa.us>
Re: Solaris initdb fails: shmmax tweak alternative? Jeff Trout <jeff@jefftrout.com>
Anyone see a benefit of adding command line flags to initdb to force
lower shared memory use without require a recompile?

Robert Treat

On Mon, 2004-04-05 at 08:53, Andrew Dunstan wrote:
> Greg Sabino Mullane said:
> >
> >
> > Having to recompile initdb.c is probably not an option.
> 
> Which version of PostreSQL are you installing on this production machine?
> initdb is not a C program in any released version - in 7.4.2 it is a shell
> script which you could trivially modify. Of course, in the next release it
> will be a C program.
> 
> cheers
> 
> andrew
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

-- 
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL


В списке pgsql-hackers по дате отправления
От: Magnus Hagander
Дата:
Сообщение: Re: 7.5 beta version
От: Jan Wieck
Дата:
Сообщение: Re: Function to kill backend
FAQ