Re: Trouble with plpgsql on 7.4.6 - Mailing list pgsql-hackers

From D'Arcy J.M. Cain
Subject Re: Trouble with plpgsql on 7.4.6
Date
Msg-id 20041118154011.36dc2ded.darcy@druid.net
Whole thread Raw
In response to Re: Trouble with plpgsql on 7.4.6  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 18 Nov 2004 14:25:41 -0500
Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "D'Arcy J.M. Cain" <darcy@druid.net> writes:
> > Has anyone else had any problem installing plpgsql into a 7.4.6
> > database?  When I try (on NetBSD 2.0RC5) I get the following
> > message:
>
> > createlang: language installation failed: server closed the
> > connection unexpectedly
>
> Probably indicates a failure to load the plpgsql shared library.

I considered that but the file is where I expect it to be.  I did this:

[pgsql@panther:/data/cert198] $ pg_config --libdir
/usr/pkg/lib

The file is actually in /usr/pkg/lib/postgresql/plpgsql.so.  I wasn't
sure if the postgresql was added so I made a symlink to assure that it
was available in both. locations.

> > I turned on a bunch of logging and this is what gets spit out into
> > the log:
>
> > Nov 18 11:49:18 panther cert198[21983]: [47-1] LOG:  00000: server
> > process (PID 7864) was terminated by signal 6
>
> There wasn't anything interesting just before that?

Not that I can see.  I have attached the entire output of the capture
from the start.  Here are the diffs from the postgresql.conf created by
initdb.

--- postgresql.conf.orig        2004-11-18 15:33:03.000000000 -0500
+++ postgresql.conf     2004-11-18 15:33:17.000000000 -0500
@@ -136,24 +136,24 @@

 # - Syslog -

-#syslog = 0                    # range 0-2; 0=stdout; 1=both; 2=syslog
-#syslog_facility = 'LOCAL0'
-#syslog_ident = 'postgres'
+syslog = 1                     # range 0-2; 0=stdout; 1=both; 2=syslog
+syslog_facility = 'LOCAL4'
+syslog_ident = 'postgres'

 # - When to Log -

-#client_min_messages = notice  # Values, in order of decreasing detail:
+client_min_messages = debug5   # Values, in order of decreasing detail:
                                #   debug5, debug4, debug3, debug2,
debug1,
                                #   log, info, notice, warning, error

-#log_min_messages = notice     # Values, in order of decreasing detail:
+log_min_messages = debug5      # Values, in order of decreasing detail:
                                #   debug5, debug4, debug3, debug2,
debug1,
                                #   info, notice, warning, error, log,
fatal,
                                #   panic

-#log_error_verbosity = default   # terse, default, or verbose messages
+log_error_verbosity = verbose   # terse, default, or verbose messages

-#log_min_error_statement = panic # Values in order of increasing
severity:
+log_min_error_statement = debug5 # Values in order of increasing
severity:
                                 #   debug5, debug4, debug3, debug2,
debug1,
                                 #   info, notice, warning, error,
panic(off)

@@ -162,7 +162,7 @@
                                 # milliseconds.  Zero prints all
queries.
                                 # Minus-one disables.

-#silent_mode = false            # DO NOT USE without Syslog!
+silent_mode = false             # DO NOT USE without Syslog!

 # - What to Log -

@@ -170,11 +170,11 @@
 #debug_print_rewritten = false
 #debug_print_plan = false
 #debug_pretty_print = false
-#log_connections = false
-#log_duration = false
-#log_pid = false
-#log_statement = false
-#log_timestamp = false
+log_connections = true
+log_duration = true
+log_pid = true
+log_statement = true
+log_timestamp = true
 #log_hostname = false
 #log_source_port = false

> Signal 6 is SIGABRT (at least on my machine) so something decided to

Same on mine.

Thanks for the help.

--
D'Arcy J.M. Cain <darcy@druid.net>         |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 425 1212     (DoD#0082)    (eNTP)   |  what's for dinner.

Attachment

pgsql-hackers by date:

Previous
From: Jan Wieck
Date:
Subject: Re: Timing of pgstats updates
Next
From: G u i d o B a r o s i o
Date:
Subject: Re: invalid page header