Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: REPOST: InitDB Failure on install
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Magnus Hagander" <mha(at)sollentuna(dot)net>
- Cc: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>, "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>, pgsql-hackers-win32(at)postgresql(dot)org
- Subject: Re: REPOST: InitDB Failure on install
- Date: Tue, 24 Aug 2004 10:37:54 -0400
- Message-id: <3323(dot)1093358274(at)sss(dot)pgh(dot)pa(dot)us>
"Magnus Hagander" <mha(at)sollentuna(dot)net> writes: > Tom - which method do you think is best to go with? I dislike propagating #ifdef WIN32's into sections of the code that are currently free of them. So I'd vote for the map-to-errno approach. It's a judgment call though ... regards, tom lane
- Follow-Ups:
- Re: REPOST: InitDB Failure on install
- From: Andreas Pflug
- Re: REPOST: InitDB Failure on install
- References:
- Re: REPOST: InitDB Failure on install
- From: Magnus Hagander
- Re: REPOST: InitDB Failure on install
- Prev by Date: Compiling 8.0beta on mingw with openssl support
- Next by Date: Re: Compiling 8.0beta on mingw with openssl support
- Previous by thread: Re: REPOST: InitDB Failure on install
- Next by thread: Re: REPOST: InitDB Failure on install
- Indexes: