PG18.6 Windows Initialization

Поиск
Список
Период
Сортировка
Искать

PG18.6 Windows Initialization

От:
sutyak <sutyak@proton.me>
Дата:
Using meson/ninja I've built PostgreSQL 18.6 using a FIPS-compliant version of OpenSSL and now I am attempting to initialize it.
After running initdb.exe it always hangs at selecting default "max_connections" ...

Any troubleshooting tips appreciated.  Nothing shows in any logs and using the debug switch doesn't provide anything additional for troubleshooting.

Mark Sutyak

Re: PG18.6 Windows Initialization

От:
Adrian Klaver <adrian.klaver@aklaver.com>
Дата:
On 10/24/26 7:50 AM, sutyak wrote:
> Using meson/ninja I've built PostgreSQL 18.6 using a FIPS-compliant 
> version of OpenSSL and now I am attempting to initialize it.
> After running initdb.exe it always hangs at selecting default 
> "max_connections" ...

You will need to give a more detailed description of what "...selecting 
default "max_connections" ..." means?

> 
> Any troubleshooting tips appreciated.  Nothing shows in any logs and 
> using the debug switch doesn't provide anything additional for 
> troubleshooting.
> 
> Mark Sutyak


-- 
Adrian Klaver
adrian.klaver@aklaver.com


Re: PG18.6 Windows Initialization

От:
sutyak <sutyak@proton.me>
Дата:
This is the full cmd output.  

C:\Users\admin\Desktop\PostgreSQL_18.6-FIPS\bin>initdb.exe
The files belonging to this database system will be owned by user "admin".
This user must also own the server process.

The database cluster will be initialized with locale "English_United States.1252".
The default database encoding has accordingly been set to "WIN1252".
The default text search configuration will be set to "english".

Data page checksums are enabled.

creating directory D:/PostgreSQL/18/data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... windows
selecting default "max_connections" ...



Mark Sutyak


On Saturday, October 24th, 2026 at 11:07 AM, Adrian Klaver  wrote:

> On 10/24/26 7:50 AM, sutyak wrote:
> > Using meson/ninja I've built PostgreSQL 18.6 using a FIPS-compliant
> > version of OpenSSL and now I am attempting to initialize it.
> > After running initdb.exe it always hangs at selecting default
> > "max_connections" ...
> 
> You will need to give a more detailed description of what "...selecting
> default "max_connections" ..." means?
> 
> >
> > Any troubleshooting tips appreciated.  Nothing shows in any logs and
> > using the debug switch doesn't provide anything additional for
> > troubleshooting.
> >
> > Mark Sutyak
> 
> 
> --
> Adrian Klaver
> adrian.klaver@aklaver.com
> 
> 
>


Re: PG18.6 Windows Initialization

От:
Adrian Klaver <adrian.klaver@aklaver.com>
Дата:
On 10/24/26 9:59 AM, sutyak wrote:
> This is the full cmd output.
> 
> C:\Users\admin\Desktop\PostgreSQL_18.6-FIPS\bin>initdb.exe
> The files belonging to this database system will be owned by user "admin".
> This user must also own the server process.
> 
> The database cluster will be initialized with locale "English_United States.1252".
> The default database encoding has accordingly been set to "WIN1252".
> The default text search configuration will be set to "english".
> 
> Data page checksums are enabled.
> 
> creating directory D:/PostgreSQL/18/data ... ok
> creating subdirectories ... ok
> selecting dynamic shared memory implementation ... windows
> selecting default "max_connections" ...

What was the complete build command you used?

Did you edit any of the files in the ~/src/ directory?

> 
> 
> 
> Mark Sutyak
> 
> 
> On Saturday, October 24th, 2026 at 11:07 AM, Adrian Klaver  wrote:
> 
>> On 10/24/26 7:50 AM, sutyak wrote:
>>> Using meson/ninja I've built PostgreSQL 18.6 using a FIPS-compliant
>>> version of OpenSSL and now I am attempting to initialize it.
>>> After running initdb.exe it always hangs at selecting default
>>> "max_connections" ...
>>
>> You will need to give a more detailed description of what "...selecting
>> default "max_connections" ..." means?
>>
>>>
>>> Any troubleshooting tips appreciated.  Nothing shows in any logs and
>>> using the debug switch doesn't provide anything additional for
>>> troubleshooting.
>>>
>>> Mark Sutyak
>>
>>
>> --
>> Adrian Klaver
>> adrian.klaver@aklaver.com
>>
>>
>>


-- 
Adrian Klaver
adrian.klaver@aklaver.com


Re: PG18.6 Windows Initialization

От:
Daniel Gustafsson <daniel@yesql.se>
Дата:
> On 24 Oct 2026, at 18:59, sutyak  wrote:

Please don't top-post, replying inline retains valuable context in the email.

> selecting default "max_connections" ...

At this point initdb.exe is trying to run postgres.exe --check with different
options to probe for what to pick, and clearly it's failing.  If you look at
test_specific_config_settings() in initdb.c you can see the command it is
trying to run, and you can attempt to run it manually to try and see what's
going on.

--
Daniel Gustafsson



Re: PG18.6 Windows Initialization

От:
sutyak <sutyak@proton.me>
Дата:



Sent from Proton Mail for Android.

-------- Original Message --------
On Saturday, 10/24/26 at 15:20 Daniel Gustafsson  wrote:
> On 24 Oct 2026, at 18:59, sutyak  wrote:

Please don't top-post, replying inline retains valuable context in the email.

> selecting default "max_connections" ...

At this point initdb.exe is trying to run postgres.exe --check with different
options to probe for what to pick, and clearly it's failing.  If you look at
test_specific_config_settings() in initdb.c you can see the command it is
trying to run, and you can attempt to run it manually to try and see what's
going on.

--
Daniel Gustafsson

That's a great lead. Thank you,  Daniel.
I'll reply back with what I find. Probably Monday.

Mark Sutyak




FAQ