Re: Postgres 7.3 from source --with-tcl : Errors again...

From: Jason Tishler <jason(at)tishler(dot)net>
To: "S(dot) L(dot)" <s0lao(at)netscape(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Andrew Klimov <and_k_98(at)yahoo(dot)com>, pgsql-cygwin(at)postgresql(dot)org
Subject: Re: Postgres 7.3 from source --with-tcl : Errors again...
Date: 2003-01-31 14:26:57
Message-ID: 20030131142657.GC736@tishler.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-cygwin

On Thu, Jan 23, 2003 at 07:51:21AM -0500, Jason Tishler wrote:
> Anyway, I started to debug the PL/Tcl problem. These are my
> observations:
>
> 1. pltcl.dll is successfully loaded by postgres
> 2. pltcl.dll is successfully loading cygtcl83.dll (which is not
> surprising since the Windows loader does this)
> 3. pltcl.dll is failing in pltcl_init_all() (which is very early in the
> initialization process)
> 4. Tcl_CreateInterp() succeeds (so at least one Tcl function seems to
> work)
> 5. Tcl_CreateSlave() fails (unfortunately, I could not determine why
> with a limited amount of effort)
>
> I will leave it to those who have the interest to continue
> debugging this problem.

I believe that I have figured out why Tcl_CreateSlave() failed above.
Since Cygwin Tcl/Tk is a hybrid Cygwin/Win32 it needs TCL_LIBRARY (and
possibly TK_LIBRARY) set with Win32 paths:

export TCL_LIBRARY=$(cygpath -w /usr/share/tcl8.4) TK_LIBRARY=$(cygpath -w /usr/share/tk8.4)

This seems to get PL/Tcl much further. However, it now fails during the
first insert with the following:

LOG: server process (pid 2960) exited with exit code 128
LOG: terminating any other active server processes
LOG: all server processes terminated; reinitializing shared memory and semaphores
IpcMemoryCreate: shmget(key=5432001, size=638976, 03600) failed: Not enough core

This error usually means that PostgreSQL's request for a shared
memory segment exceeded available memory or swap space.
To reduce the request size (currently 638976 bytes), reduce
PostgreSQL's shared_buffers parameter (currently 16) and/or
its max_connections parameter (currently 4).

The PostgreSQL Administrator's Guide contains more information about
shared memory configuration.

Unfortunately, the standard fix of increasing

HKCU\Software\Cygnus Solutions\Cygwin\heap_chunk_in_mb

doesn't seem to help. :,(

Jason

--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6

In response to

Browse pgsql-cygwin by date

  From Date Subject
Next Message Jason Tishler 2003-01-31 20:38:54 Re: IpcSemaphoreCreate
Previous Message Cornelia Boenigk 2003-01-31 12:16:12 Re: How to solve error IpcSemaphoreCreate in Cygwin