Thread: Re: /usr/bin/postmaster -D /usr/local/pgsql/data RESULTS IN A CORE DUMP
Re: /usr/bin/postmaster -D /usr/local/pgsql/data RESULTS IN A CORE DUMP
From
Vladimir Tsvetkov
Date:
> I've had just to change the following option for cygserver: > /etc/cygserver.conf > > # kern.ipc.semmns: Maximum no. of semaphores hold concurrently. > # Default: 60, Min: 1, Max: 1024 > #kern.ipc..semmns 60 > kern.ipc..semmns 512 > > And after this the initdb procedure worked without failure. OK. initdb works: [SAMUIL@vlado_1 /home/SAMUIL]> initdb -D /usr/local/pgsql/data -W -E LATIN1 The files belonging to this database system will be owned by user "SAMUIL". This user must also own the server process. The database cluster will be initialized with locale C. creating directory /usr/local/pgsql/data... ok creating directory /usr/local/pgsql/data/base... ok creating directory /usr/local/pgsql/data/global... ok creating directory /usr/local/pgsql/data/pg_xlog... ok creating directory /usr/local/pgsql/data/pg_clog... ok selecting default max_connections... 100 selecting default shared_buffers... 1000 creating configuration files... ok creating template1 database in /usr/local/pgsql/data/base/1... ok initializing pg_shadow... ok Enter new superuser password: Enter it again: setting password... ok enabling unlimited row size for system tables... ok initializing pg_depend... ok creating system views... ok loading pg_description... ok creating conversions... ok setting privileges on built-in objects... ok creating information schema... ok vacuuming database template1... ok copying template1 to template0... ok Success. You can now start the database server using: /usr/bin/postmaster -D /usr/local/pgsql/data or /usr/bin/pg_ctl -D /usr/local/pgsql/data -l logfile start But when I try to start up the postmaster I get a nasty core dump: [SAMUIL@vlado_1 /home/SAMUIL]> /usr/bin/postmaster -D /usr/local/pgsql/data Segmentation fault (core dumped) [SAMUIL@vlado_1 /home/SAMUIL]> cat postgres.exe.stackdump Exception: STATUS_ACCESS_VIOLATION at eip=610028AA eax=00000000 ebx=61258E78 ecx=0000000A edx=000001A8 esi=000001A8 edi=61259000 ebp=0022E948 esp=0022E910 program=C:\cygwin\bin\postgres.exe, pid 884, thread ma in cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023 Stack trace: Frame Function Args 0022E948 610028AA (00000000, 61258C78, 0022E978, 6101F5E8) 0022E978 6101171C (611572C0, 61258C78, 0022E9C8, 61010F4E) 0022E9A8 61011CED (61154A78, 61157280, 611D85C8, 61154A78) 0022E9E8 61011E38 (61154A78, 00000000, 000007B5, 00002000) 0022EA28 6108E3FD (00000000, 00002000, 0022EA68, 10010158) 0022EA58 610844FF (0022EA78, 0022EA7C, 0022EA88, 0053F2C3) 0022EA88 0055945A (00001538, 00000000, 00001538, 10016610) 0022EEE8 0053D258 (00000003, 100101B8, 00000764, 61087959) 0022EF18 00506FFD (00000003, 611574B0, 10010090, 77F79005) 0022EFD8 61004DD2 (0022EFF0, 00000000, 0022F221, 31373838) 0022FF88 6100594F (00000000, 00000000, 00000000, 00000000) End of stack trace Is there any way to fix this error? Best Regards, Vladimir Tsvetkov