Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] initdb

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "Postgresql Hackers" <pgsql-hackers(at)postgresql(dot)org>,"pgsql-hackers-win32" <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: [HACKERS] initdb
Date: 2003-10-12 17:13:41
Message-ID: 003101c390e4$2fe81cf0$6401a8c0@DUNSLANE (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-hackers-win32pgsql-patches
Bruce,

I think this is now ready to import into the WIN32 branch. I have ironed out
the cygwin dependencies, and posted a note about what we'll need to do
inside postgres to handle the environment values for setlocale() on Windows.

If you want to rip out the unlink stuff (see previous email thread) we'll
need a version of dirmod.c that is compiled with -DFRONTEND - I guess libpq
is the obvious place for that.

Apart from initdb.c we'll need the file system_views.sql, which can be taken
without change (unless someone want to add comments to it), and Makefile
modifications (see my Makefile on the web for an example, but it probably
doesn't comply with our standard way of doing things).

Anything broken can then be fixed with patches - I have about 7 versions on
5 machines now and my head is starting to swim -).

pg_id and pg_encoding now become redundant in their entirety, as does
initdb.sh.

cheers

andrew


----- Original Message ----- 
From: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
Cc: "Postgresql Hackers" <pgsql-hackers(at)postgresql(dot)org>;
"pgsql-hackers-win32" <pgsql-hackers-win32(at)postgresql(dot)org>
Sent: Thursday, October 09, 2003 10:07 PM
Subject: Re: [pgsql-hackers-win32] [HACKERS] initdb


> Andrew Dunstan wrote:
> > There will be a new version out there soon. When I am happy with it I
will
> > let you know - right now I am dealing with 2 issues -
setlocale(LC_ALL,"")
> > doesn't read from the environment on Windows, and the program is
possibly
> > not picking up the buffers/connections properly.
> >
> > Please don't put the version currently out there in CVS - the files
won't
> > even be the same - initdb-scripts.h will disappear and there will be a
new
> > file called "system_views.sql".
> >
> > There is no urgency about this - until we have a working postgres
executable
> > on Windows initdb is useless anyway. My aim has been to have initdb
ready
> > when postgres is ready. Of course, I test against Unix all the time to
make
> > sure nothing gets broken.
>
> Fine.  We have the URL on the win32 web site, and that's all we need.
>
> -- 
>   Bruce Momjian                        |  http://candle.pha.pa.us
>   pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
>   +  If your life is a hard drive,     |  13 Roberts Road
>   +  Christ can be your backup.        |  Newtown Square, Pennsylvania
19073
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
>       message can get through to the mailing list cleanly


In response to

Responses

  • initdb in C at 2003-11-08 05:15:42 from Bruce Momjian

pgsql-hackers by date

Next:From: Marc G. FournierDate: 2003-10-12 19:03:02
Subject: Re: http://www.pgsql.com/register/submit.php
Previous:From: Tom LaneDate: 2003-10-12 16:55:54
Subject: Re: http://www.pgsql.com/register/submit.php

pgsql-patches by date

Next:From: Peter EisentrautDate: 2003-10-12 19:17:51
Subject: Re: libpq Italian Version first translation
Previous:From: veramente@libero.itDate: 2003-10-12 16:42:27
Subject: psql IT updates

pgsql-hackers-win32 by date

Next:From: Tommi MaekitaloDate: 2003-10-23 08:29:15
Subject: pg_ctl reports succes when start fails
Previous:From: Andrew DunstanDate: 2003-10-10 17:37:53
Subject: Re: signals on windows

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group