Awesome! Thanks so much for the fix -- I depend on PostgreSQL and Tcl
on my powerbook to do development work.
cheers,
/s.
On Nov 8, 2003, at 2:09 PM, Tom Lane wrote:
It turns out that the "createlang pltcl" failure on OS X 10.3 was due
to
our ps_status code doing the wrong thing. I have comm
After recompiling with GCC 3.1 it fails when I'm running initdb to
create the cluster -- it's a shmget error again. I believe that takes
both Tcl and PostgreSQL out of the suspect pool and leaves Mac OS 10.3
as the primary culprit. I installed Panther last week from scratch
(reformatted disk et
Just compiled PG 7.3.4 with GCC 3.1 on Panther and it exhibits the same
problem, but generates a SIGSEGV instead of a SIGBUS. Here's the log:
LOG: server process (pid 12078) was terminated by signal 11
LOG: terminating any other active server processes
LOG: all server processes terminated; rei
Hi Tom,
On Nov 4, 2003, at 4:48 PM, Tom Lane wrote:
Here's the code that triggers it:
create function pltcl_call_handler() RETURNS LANGUAGE_HANDLER
as 'pltcl.so' language 'c';
I don't think so. That's a startup failure; it can not be triggered by
executing a SQL command, because if the postm
It turns out that the "createlang pltcl" failure on OS X 10.3 was due to
our ps_status code doing the wrong thing. I have committed a fix.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once w
Scott Goodwin <[EMAIL PROTECTED]> writes:
> Just compiled PG 7.3.4 with GCC 3.1 on Panther and it exhibits the same
> problem, but generates a SIGSEGV instead of a SIGBUS.
I tried this on the 10.3 beta that I have (from about a month back) and
indeed I get a core dump while trying to create the
Scott Goodwin <[EMAIL PROTECTED]> writes:
> After recompiling with GCC 3.1 it fails when I'm running initdb to
> create the cluster -- it's a shmget error again. I believe that takes
> both Tcl and PostgreSQL out of the suspect pool and leaves Mac OS 10.3
> as the primary culprit.
Does the fail
Scott Goodwin <[EMAIL PROTECTED]> writes:
> psql:/Users/scott/m/ops/database/sql/add_languages.sql:13: server
> closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> ...output in the log file is:
>
Scott Goodwin <[EMAIL PROTECTED]> writes:
> FATAL: could not create shared memory segment: Cannot allocate memory
> Here's the code that triggers it:
> create function pltcl_call_handler() RETURNS LANGUAGE_HANDLER
> as 'pltcl.so' language 'c';
I don't think so. That's a startup failure; it
I've encountered a problem where the PostgreSQL database crashes when
attempting to load pltcl.so on Mac OS 10.3. PostgreSQL fails because
memory cannot be allocated during a shmget call. Here is the exact
error message:
FATAL: could not create shared memory segment: Cannot allocate memory
DET
10 matches
Mail list logo
