Thread: beta3 winxp initdb problems

beta3 winxp initdb problems

From
"BARTKO, Zoltán"
Date:
Hello, folks,

I am trying to install pgsql8 on winxp. I tried first to install "as
is" with pginstaller beta2-dev3, no luck, it froze, switched off
Nod32, froze a little later, ran through the list of services,
switched off anything that seemed to be a firewall, no luck.

So I compiled beta3 with mingw, installed, and now initdb keeps
telling me this:

<listing>
Microsoft Windows XP [Verzia 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\WINDOWS\system32>d:
<snip/>
D:\tmp\data>initdb
The files belonging to this database system will be owned by user
"postgresql".
This user must also own the server process.

The database cluster will be initialized with locale Slovak_Slovakia.1250.

fixing permissions on existing directory d:/tmp/data ... ok
creating directory d:/tmp/data/global ... ok
creating directory d:/tmp/data/pg_xlog ... ok
creating directory d:/tmp/data/pg_xlog/archive_status ... ok
creating directory d:/tmp/data/pg_clog ... ok
creating directory d:/tmp/data/pg_subtrans ... ok
creating directory d:/tmp/data/base ... ok
creating directory d:/tmp/data/base/1 ... ok
creating directory d:/tmp/data/pg_tblspc ... ok
selecting default max_connections ... 10
selecting default shared_buffers ... 50
creating configuration files ... ok
creating template1 database in d:/tmp/data/base/1 ... FATAL:  could
not select a
 suitable default timezone
DETAIL:  It appears that your GMT time zone uses leap seconds.
PostgreSQL does n
ot support leap seconds.
child process was terminated by signal 1
initdb: failed
initdb: removing contents of data directory "d:/tmp/data"

D:\tmp\data>

</listing>

now, beta2 reported no problems with initdb, it just never finished
the installation and even if I tell my computer I am located in
London, UK, use Greenwich Mean Time, I still get this fatal error.

I have no idea what to do...

please, give me some advice.

Thanks in advance

Zoltan

====================== REKLAMA ========================
Spolocnost SUN Microsystems uviedla na trh novy server Sun Fire V20z
zalozeny procesoroch AMD Opteron.
Viac informacii najdete na : http://www.somi.sk/sun/v20z.php
=======================================================


Re: beta3 winxp initdb problems

From
"Magnus Hagander"
Date:
> Hello, folks,
>
> I am trying to install pgsql8 on winxp. I tried first to install "as
> is" with pginstaller beta2-dev3, no luck, it froze, switched off
> Nod32, froze a little later, ran through the list of services,
> switched off anything that seemed to be a firewall, no luck.
>
> So I compiled beta3 with mingw, installed, and now initdb keeps
> telling me this:
>
> <listing>
> Microsoft Windows XP [Verzia 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\WINDOWS\system32>d:
> <snip/>
> D:\tmp\data>initdb
> The files belonging to this database system will be owned by user
> "postgresql".
> This user must also own the server process.
>
> The database cluster will be initialized with locale
> Slovak_Slovakia.1250.
>
> fixing permissions on existing directory d:/tmp/data ... ok
> creating directory d:/tmp/data/global ... ok
> creating directory d:/tmp/data/pg_xlog ... ok
> creating directory d:/tmp/data/pg_xlog/archive_status ... ok
> creating directory d:/tmp/data/pg_clog ... ok
> creating directory d:/tmp/data/pg_subtrans ... ok
> creating directory d:/tmp/data/base ... ok
> creating directory d:/tmp/data/base/1 ... ok
> creating directory d:/tmp/data/pg_tblspc ... ok
> selecting default max_connections ... 10
> selecting default shared_buffers ... 50
> creating configuration files ... ok
> creating template1 database in d:/tmp/data/base/1 ... FATAL:  could
> not select a
>  suitable default timezone
> DETAIL:  It appears that your GMT time zone uses leap seconds.
> PostgreSQL does n
> ot support leap seconds.
> child process was terminated by signal 1
> initdb: failed
> initdb: removing contents of data directory "d:/tmp/data"
>
> D:\tmp\data>
>
> </listing>
>
> now, beta2 reported no problems with initdb, it just never finished
> the installation and even if I tell my computer I am located in
> London, UK, use Greenwich Mean Time, I still get this fatal error.

Hello!

Could you please run this with debugging enabled? You do this by passing "-d" to initdb.
The interesting output is the stuff that comes between the "creating template1 database" message and the FATAL error.

Did you restart the commandprompt you ran initdb in after changing the timezone?

//Magnus


Re: beta3 winxp initdb problems

From
"BARTKO, Zoltán"
Date:
Magnus, et al.,

This is, what initdb -d says:

<listing>

D:\tmp\data>initdb -d
Running in debug mode.
VERSION=8.0.0beta3
PGDATA=d:/tmp/data
share_path=c:/msys/1.0/share/postgresql
PGPATH=c:/msys/1.0/bin
POSTGRES_SUPERUSERNAME=postgresql
POSTGRES_BKI=c:/msys/1.0/share/postgresql/postgres.bki
POSTGRES_DESCR=c:/msys/1.0/share/postgresql/postgres.description
POSTGRESQL_CONF_SAMPLE=c:/msys/1.0/share/postgresql/postgresql.conf.sample
PG_HBA_SAMPLE=c:/msys/1.0/share/postgresql/pg_hba.conf.sample
PG_IDENT_SAMPLE=c:/msys/1.0/share/postgresql/pg_ident.conf.sample
The files belonging to this database system will be owned by user
"postgresql".
This user must also own the server process.

The database cluster will be initialized with locale Slovak_Slovakia.1250.

fixing permissions on existing directory d:/tmp/data ... ok
creating directory d:/tmp/data/global ... ok
creating directory d:/tmp/data/pg_xlog ... ok
creating directory d:/tmp/data/pg_xlog/archive_status ... ok
creating directory d:/tmp/data/pg_clog ... ok
creating directory d:/tmp/data/pg_subtrans ... ok
creating directory d:/tmp/data/base ... ok
creating directory d:/tmp/data/base/1 ... ok
creating directory d:/tmp/data/pg_tblspc ... ok
selecting default max_connections ... 10
selecting default shared_buffers ... 50
creating configuration files ... ok
creating template1 database in d:/tmp/data/base/1 ... DEBUG:  TZ
"Europe/Belgrad
e" matches Windows timezone "Central Europe Daylight Time"
FATAL:  could not select a suitable default timezone
DETAIL:  It appears that your GMT time zone uses leap seconds. PostgreSQL
does n
ot support leap seconds.
DEBUG:  proc_exit(1)
DEBUG:  shmem_exit(1)
DEBUG:  exit(1)
child process was terminated by signal 1
initdb: failed
initdb: removing contents of data directory "d:/tmp/data"

D:\tmp\data>
</listing>

So I said to myself, set the timezone to GMT. This, what I got after
switching off the automatic daylight saving time notification:

<listing>
D:\tmp\data>initdb -d
Running in debug mode.
VERSION=8.0.0beta3
PGDATA=d:/tmp/data
share_path=c:/msys/1.0/share/postgresql
PGPATH=c:/msys/1.0/bin
POSTGRES_SUPERUSERNAME=postgresql
POSTGRES_BKI=c:/msys/1.0/share/postgresql/postgres.bki
POSTGRES_DESCR=c:/msys/1.0/share/postgresql/postgres.description
POSTGRESQL_CONF_SAMPLE=c:/msys/1.0/share/postgresql/postgresql.conf.sample
PG_HBA_SAMPLE=c:/msys/1.0/share/postgresql/pg_hba.conf.sample
PG_IDENT_SAMPLE=c:/msys/1.0/share/postgresql/pg_ident.conf.sample
The files belonging to this database system will be owned by user
"postgresql".
This user must also own the server process.

The database cluster will be initialized with locale Slovak_Slovakia.1250.

fixing permissions on existing directory d:/tmp/data ... ok
creating directory d:/tmp/data/global ... ok
creating directory d:/tmp/data/pg_xlog ... ok
creating directory d:/tmp/data/pg_xlog/archive_status ... ok
creating directory d:/tmp/data/pg_clog ... ok
creating directory d:/tmp/data/pg_subtrans ... ok
creating directory d:/tmp/data/base ... ok
creating directory d:/tmp/data/base/1 ... ok
creating directory d:/tmp/data/pg_tblspc ... ok
selecting default max_connections ... 10
selecting default shared_buffers ... 50
creating configuration files ... ok
creating template1 database in d:/tmp/data/base/1 ... DEBUG:  TZ
"Europe/Dublin"
 matches Windows timezone "GMT Standard Time"
FATAL:  could not select a suitable default timezone
DETAIL:  It appears that your GMT time zone uses leap seconds. PostgreSQL
does n
ot support leap seconds.
DEBUG:  proc_exit(1)
DEBUG:  shmem_exit(1)
DEBUG:  exit(1)
child process was terminated by signal 1
initdb: failed
initdb: removing contents of data directory "d:/tmp/data"

D:\tmp\data>
</listing>

Any ideas?

Zoltan


>
> Hello!
>
> Could you please run this with debugging enabled? You do this by passing
> "-d" to initdb.
> The interesting output is the stuff that comes between the "creating
> template1 database" message and the FATAL error.
>
> Did you restart the commandprompt you ran initdb in after changing the
> timezone?
>
> //Magnus
>
>




____________________________________
http://www.pobox.sk/ - najvacsi slovensky freemail




Re: beta3 winxp initdb problems

From
Piotr Filipczuk
Date:
Hi.

I understand that you are using NOD32 software. To correct install
postgres you must first uninstall IMON from NOD32.
IMON is som how intgerete with windows socket and somehow brake
communication with postgresql database.

Piotr Filipczuk

BARTKO, Zoltán wrote:

>Hello, folks,
>
>I am trying to install pgsql8 on winxp. I tried first to install "as
>is" with pginstaller beta2-dev3, no luck, it froze, switched off
>Nod32, froze a little later, ran through the list of services,
>switched off anything that seemed to be a firewall, no luck.
>
>So I compiled beta3 with mingw, installed, and now initdb keeps
>telling me this:
>
><listing>
>Microsoft Windows XP [Verzia 5.1.2600]
>(C) Copyright 1985-2001 Microsoft Corp.
>
>C:\WINDOWS\system32>d:
><snip/>
>D:\tmp\data>initdb
>The files belonging to this database system will be owned by user
>"postgresql".
>This user must also own the server process.
>
>The database cluster will be initialized with locale Slovak_Slovakia.1250.
>
>fixing permissions on existing directory d:/tmp/data ... ok
>creating directory d:/tmp/data/global ... ok
>creating directory d:/tmp/data/pg_xlog ... ok
>creating directory d:/tmp/data/pg_xlog/archive_status ... ok
>creating directory d:/tmp/data/pg_clog ... ok
>creating directory d:/tmp/data/pg_subtrans ... ok
>creating directory d:/tmp/data/base ... ok
>creating directory d:/tmp/data/base/1 ... ok
>creating directory d:/tmp/data/pg_tblspc ... ok
>selecting default max_connections ... 10
>selecting default shared_buffers ... 50
>creating configuration files ... ok
>creating template1 database in d:/tmp/data/base/1 ... FATAL:  could
>not select a
> suitable default timezone
>DETAIL:  It appears that your GMT time zone uses leap seconds.
>PostgreSQL does n
>ot support leap seconds.
>child process was terminated by signal 1
>initdb: failed
>initdb: removing contents of data directory "d:/tmp/data"
>
>D:\tmp\data>
>
></listing>
>
>now, beta2 reported no problems with initdb, it just never finished
>the installation and even if I tell my computer I am located in
>London, UK, use Greenwich Mean Time, I still get this fatal error.
>
>I have no idea what to do...
>
>please, give me some advice.
>
>Thanks in advance
>
>Zoltan
>
>====================== REKLAMA ========================
>Spolocnost SUN Microsystems uviedla na trh novy server Sun Fire V20z
>zalozeny procesoroch AMD Opteron.
>Viac informacii najdete na : http://www.somi.sk/sun/v20z.php
>=======================================================
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
>    (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
>
>


Another list for windows port...

From
Eric
Date:
It is possible to mainteners of this list to keep this list from
"/$?%/$?/? windows problems?  I don't care about windows.  The worst
thing never made was porting an excellent product like PostgreSQL to a
poor server OS like windows.

Now, we are invade with users that aren't used to read the manual...
even the howto install readme!!!  Users that have problems often relate
to bug in OS...

I thought the topic of this list was to postgresql in general and not
about WINDOWS SPECIFIQ PART.

So the solution is to do another list for them...

My opinion.



Re: Another list for windows port...

From
"Joshua D. Drake"
Date:
Eric wrote:

>It is possible to mainteners of this list to keep this list from
>"/$?%/$?/? windows problems?  I don't care about windows.  The worst
>thing never made was porting an excellent product like PostgreSQL to a
>poor server OS like windows.
>
>Now, we are invade with users that aren't used to read the manual...
>
>
You mean like most Linux users?

>I thought the topic of this list was to postgresql in general and not
>about WINDOWS SPECIFIQ PART.
>
>
It is general, which is why you get a lot of cross traffic. If you want
to see more specific topics you may
want to try the more specific lsits.

>So the solution is to do another list for them...
>
>
Uhm there is a list for them.

Remember the goal is the pervasiveness of PostgreSQL -- regardless of
platform.

Sincerely,

Joshua D. Drake



>My opinion.
>
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>
>


--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL


Re: Another list for windows port...

From
Robby Russell
Date:
On Mon, 2004-10-18 at 17:38 -0400, Eric wrote:
> The worst
> thing never made was porting an excellent product like PostgreSQL to a
> poor server OS like windows.

Isn't the purpose to promote PostgreSQL? not *nix-only flavors?

Hmm..other open source projects that run on Windows servers... apache,
mysql, php, python, perl, etc etc etc... Porting it to Windows is a
great thing.. the more that open source gets its way into the use of all
markets, the more acceptable it becomes in the mainstream..and the less
control companies like Microsoft have on the markets.

my 2 cents,

Robby

--
/***************************************
* Robby Russell | Owner.Developer.Geek
* PLANET ARGON  | www.planetargon.com
* Portland, OR  | robby@planetargon.com
* 503.351.4730  | blog.planetargon.com
* PHP/PostgreSQL Hosting & Development
****************************************/


Attachment

Re: Another list for windows port...

From
"Joshua D. Drake"
Date:
>Hmm..other open source projects that run on Windows servers... apache,
>mysql, php, python, perl, etc etc etc... Porting it to Windows is a
>great thing.. the more that open source gets its way into the use of all
>markets, the more acceptable it becomes in the mainstream..and the less
>control companies like Microsoft have on the markets.
>
>
And besides if Microsoft is the enemy, the easiest way to beat them, is
to make free, suitable replacements
on their own platform ;)


>my 2 cents,
>
>Robby
>
>
>


--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL


Re: beta3 winxp initdb problems

From
bartkoedith@internetkosice.sk
Date:
Magnus, et al.,

This is, what initdb -d says:

<listing>

D:\tmp\data>initdb -d
Running in debug mode.
VERSION=8.0.0beta3
PGDATA=d:/tmp/data
share_path=c:/msys/1.0/share/postgresql
PGPATH=c:/msys/1.0/bin
POSTGRES_SUPERUSERNAME=postgresql
POSTGRES_BKI=c:/msys/1.0/share/postgresql/postgres.bki
POSTGRES_DESCR=c:/msys/1.0/share/postgresql/postgres.description
POSTGRESQL_CONF_SAMPLE=c:/msys/1.0/share/postgresql/postgresql.conf.sample
PG_HBA_SAMPLE=c:/msys/1.0/share/postgresql/pg_hba.conf.sample
PG_IDENT_SAMPLE=c:/msys/1.0/share/postgresql/pg_ident.conf.sample
The files belonging to this database system will be owned by user
"postgresql".
This user must also own the server process.

The database cluster will be initialized with locale Slovak_Slovakia.1250.

fixing permissions on existing directory d:/tmp/data ... ok
creating directory d:/tmp/data/global ... ok
creating directory d:/tmp/data/pg_xlog ... ok
creating directory d:/tmp/data/pg_xlog/archive_status ... ok
creating directory d:/tmp/data/pg_clog ... ok
creating directory d:/tmp/data/pg_subtrans ... ok
creating directory d:/tmp/data/base ... ok
creating directory d:/tmp/data/base/1 ... ok
creating directory d:/tmp/data/pg_tblspc ... ok
selecting default max_connections ... 10
selecting default shared_buffers ... 50
creating configuration files ... ok
creating template1 database in d:/tmp/data/base/1 ... DEBUG:  TZ
"Europe/Belgrad
e" matches Windows timezone "Central Europe Daylight Time"
FATAL:  could not select a suitable default timezone
DETAIL:  It appears that your GMT time zone uses leap seconds. PostgreSQL
does n
ot support leap seconds.
DEBUG:  proc_exit(1)
DEBUG:  shmem_exit(1)
DEBUG:  exit(1)
child process was terminated by signal 1
initdb: failed
initdb: removing contents of data directory "d:/tmp/data"

D:\tmp\data>
</listing>

So I said to myself, set the timezone to GMT. This, what I got after
switching off the automatic daylight saving time notification:

<listing>
D:\tmp\data>initdb -d
Running in debug mode.
VERSION=8.0.0beta3
PGDATA=d:/tmp/data
share_path=c:/msys/1.0/share/postgresql
PGPATH=c:/msys/1.0/bin
POSTGRES_SUPERUSERNAME=postgresql
POSTGRES_BKI=c:/msys/1.0/share/postgresql/postgres.bki
POSTGRES_DESCR=c:/msys/1.0/share/postgresql/postgres.description
POSTGRESQL_CONF_SAMPLE=c:/msys/1.0/share/postgresql/postgresql.conf.sample
PG_HBA_SAMPLE=c:/msys/1.0/share/postgresql/pg_hba.conf.sample
PG_IDENT_SAMPLE=c:/msys/1.0/share/postgresql/pg_ident.conf.sample
The files belonging to this database system will be owned by user
"postgresql".
This user must also own the server process.

The database cluster will be initialized with locale Slovak_Slovakia.1250.

fixing permissions on existing directory d:/tmp/data ... ok
creating directory d:/tmp/data/global ... ok
creating directory d:/tmp/data/pg_xlog ... ok
creating directory d:/tmp/data/pg_xlog/archive_status ... ok
creating directory d:/tmp/data/pg_clog ... ok
creating directory d:/tmp/data/pg_subtrans ... ok
creating directory d:/tmp/data/base ... ok
creating directory d:/tmp/data/base/1 ... ok
creating directory d:/tmp/data/pg_tblspc ... ok
selecting default max_connections ... 10
selecting default shared_buffers ... 50
creating configuration files ... ok
creating template1 database in d:/tmp/data/base/1 ... DEBUG:  TZ
"Europe/Dublin"
 matches Windows timezone "GMT Standard Time"
FATAL:  could not select a suitable default timezone
DETAIL:  It appears that your GMT time zone uses leap seconds. PostgreSQL
does n
ot support leap seconds.
DEBUG:  proc_exit(1)
DEBUG:  shmem_exit(1)
DEBUG:  exit(1)
child process was terminated by signal 1
initdb: failed
initdb: removing contents of data directory "d:/tmp/data"

D:\tmp\data>
</listing>

Any ideas?

Zoltan


>
> Hello!
>
> Could you please run this with debugging enabled? You do this by passing
> "-d" to initdb.
> The interesting output is the stuff that comes between the "creating
> template1 database" message and the FATAL error.
>
> Did you restart the commandprompt you ran initdb in after changing the
> timezone?
>
> //Magnus
>
>


Re: Another list for windows port...

From
Peter Eisentraut
Date:
Am Dienstag, 19. Oktober 2004 02:31 schrieb Robby Russell:
> Isn't the purpose to promote PostgreSQL? not *nix-only flavors?

It could be argued that the purpose is to get one's job done.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

Re: Another list for windows port...

From
"Raymond O'Donnell"
Date:
On 18 Oct 2004 at 17:38, Eric wrote:

> It is possible to mainteners of this list to keep this list from
> "/$?%/$?/? windows problems?  I don't care about windows.  The worst
> thing never made was porting an excellent product like PostgreSQL to a
> poor server OS like windows.
>
> Now, we are invade with users that aren't used to read the manual...
> even the howto install readme!!!  Users that have problems often relate
> to bug in OS...

It's very unfair to confuse users of Windows with users who don't
RTFM.

The opinion expressed above is also totally at odds with what I have
come to expect on this list - friendly, professional, expert help,
not to mention reasoned debate.

--Ray.

-------------------------------------------------------------
Raymond O'Donnell     http://www.galwaycathedral.org/recitals
rod@iol.ie                          Galway Cathedral Recitals
-------------------------------------------------------------



Re: Another list for windows port...

From
Jan Wieck
Date:
On 10/19/2004 7:11 AM, Raymond O'Donnell wrote:

> On 18 Oct 2004 at 17:38, Eric wrote:
>
>> It is possible to mainteners of this list to keep this list from
>> "/$?%/$?/? windows problems?  I don't care about windows.  The worst
>> thing never made was porting an excellent product like PostgreSQL to a
>> poor server OS like windows.
>>
>> Now, we are invade with users that aren't used to read the manual...
>> even the howto install readme!!!  Users that have problems often relate
>> to bug in OS...
>
> It's very unfair to confuse users of Windows with users who don't
> RTFM.
>
> The opinion expressed above is also totally at odds with what I have
> come to expect on this list - friendly, professional, expert help,
> not to mention reasoned debate.

The PostgreSQL team has not spent a great deal of effort porting the
database system to the Win32 platform in order to have people like Eric
spoil the reputation of our mailing lists.

If Eric doesn't care about windows, he can ignore discussions related to
it. If he doesn't want to see messages related to it, maybe he can show
his capabilities to RTFM by setting up appropriate procmail filters. Or
does this sound too difficult to you, Eric?


Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #

Re: beta3 winxp initdb problems

From
"Magnus Hagander"
Date:
Speaking off-list with Zoltan, it appears this problem was *also*
related to nod32 antivirus. Just a different error message than we've
seen before. Seems nod32 is significantly worse than any other AV
products for postgresql...

//Magnus

> -----Original Message-----
> From: bartkoedith@internetkosice.sk
> [mailto:bartkoedith@internetkosice.sk]
> Sent: Thursday, October 14, 2004 9:34 AM
> To: pgsql-general@postgresql.org
> Cc: Magnus Hagander
> Subject: Re: [GENERAL] beta3 winxp initdb problems
>
> Magnus, et al.,
>
> This is, what initdb -d says:
>
> <listing>
>
> D:\tmp\data>initdb -d
> Running in debug mode.
> VERSION=8.0.0beta3
> PGDATA=d:/tmp/data
> share_path=c:/msys/1.0/share/postgresql
> PGPATH=c:/msys/1.0/bin
> POSTGRES_SUPERUSERNAME=postgresql
> POSTGRES_BKI=c:/msys/1.0/share/postgresql/postgres.bki
> POSTGRES_DESCR=c:/msys/1.0/share/postgresql/postgres.description
> POSTGRESQL_CONF_SAMPLE=c:/msys/1.0/share/postgresql/postgresql
> .conf.sample
> PG_HBA_SAMPLE=c:/msys/1.0/share/postgresql/pg_hba.conf.sample
> PG_IDENT_SAMPLE=c:/msys/1.0/share/postgresql/pg_ident.conf.sample
> The files belonging to this database system will be owned by
> user "postgresql".
> This user must also own the server process.
>
> The database cluster will be initialized with locale
> Slovak_Slovakia.1250.
>
> fixing permissions on existing directory d:/tmp/data ... ok
> creating directory d:/tmp/data/global ... ok creating
> directory d:/tmp/data/pg_xlog ... ok creating directory
> d:/tmp/data/pg_xlog/archive_status ... ok creating directory
> d:/tmp/data/pg_clog ... ok creating directory
> d:/tmp/data/pg_subtrans ... ok creating directory
> d:/tmp/data/base ... ok creating directory d:/tmp/data/base/1
> ... ok creating directory d:/tmp/data/pg_tblspc ... ok
> selecting default max_connections ... 10 selecting default
> shared_buffers ... 50 creating configuration files ... ok
> creating template1 database in d:/tmp/data/base/1 ... DEBUG:
> TZ "Europe/Belgrad e" matches Windows timezone "Central
> Europe Daylight Time"
> FATAL:  could not select a suitable default timezone
> DETAIL:  It appears that your GMT time zone uses leap
> seconds. PostgreSQL does n ot support leap seconds.
> DEBUG:  proc_exit(1)
> DEBUG:  shmem_exit(1)
> DEBUG:  exit(1)
> child process was terminated by signal 1
> initdb: failed
> initdb: removing contents of data directory "d:/tmp/data"
>
> D:\tmp\data>
> </listing>
>
> So I said to myself, set the timezone to GMT. This, what I
> got after switching off the automatic daylight saving time
> notification:
>
> <listing>
> D:\tmp\data>initdb -d
> Running in debug mode.
> VERSION=8.0.0beta3
> PGDATA=d:/tmp/data
> share_path=c:/msys/1.0/share/postgresql
> PGPATH=c:/msys/1.0/bin
> POSTGRES_SUPERUSERNAME=postgresql
> POSTGRES_BKI=c:/msys/1.0/share/postgresql/postgres.bki
> POSTGRES_DESCR=c:/msys/1.0/share/postgresql/postgres.description
> POSTGRESQL_CONF_SAMPLE=c:/msys/1.0/share/postgresql/postgresql
> .conf.sample
> PG_HBA_SAMPLE=c:/msys/1.0/share/postgresql/pg_hba.conf.sample
> PG_IDENT_SAMPLE=c:/msys/1.0/share/postgresql/pg_ident.conf.sample
> The files belonging to this database system will be owned by
> user "postgresql".
> This user must also own the server process.
>
> The database cluster will be initialized with locale
> Slovak_Slovakia.1250.
>
> fixing permissions on existing directory d:/tmp/data ... ok
> creating directory d:/tmp/data/global ... ok creating
> directory d:/tmp/data/pg_xlog ... ok creating directory
> d:/tmp/data/pg_xlog/archive_status ... ok creating directory
> d:/tmp/data/pg_clog ... ok creating directory
> d:/tmp/data/pg_subtrans ... ok creating directory
> d:/tmp/data/base ... ok creating directory d:/tmp/data/base/1
> ... ok creating directory d:/tmp/data/pg_tblspc ... ok
> selecting default max_connections ... 10 selecting default
> shared_buffers ... 50 creating configuration files ... ok
> creating template1 database in d:/tmp/data/base/1 ... DEBUG:
> TZ "Europe/Dublin"
>  matches Windows timezone "GMT Standard Time"
> FATAL:  could not select a suitable default timezone
> DETAIL:  It appears that your GMT time zone uses leap
> seconds. PostgreSQL does n ot support leap seconds.
> DEBUG:  proc_exit(1)
> DEBUG:  shmem_exit(1)
> DEBUG:  exit(1)
> child process was terminated by signal 1
> initdb: failed
> initdb: removing contents of data directory "d:/tmp/data"
>
> D:\tmp\data>
> </listing>
>
> Any ideas?
>
> Zoltan
>
>
> >
> > Hello!
> >
> > Could you please run this with debugging enabled? You do this by
> > passing "-d" to initdb.
> > The interesting output is the stuff that comes between the "creating
> > template1 database" message and the FATAL error.
> >
> > Did you restart the commandprompt you ran initdb in after
> changing the
> > timezone?
> >
> > //Magnus
> >
> >
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>