Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 0CB4E9FB311 for ; Sat, 9 Jun 2007 18:15:20 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 58329-01 for ; Sat, 9 Jun 2007 18:15:12 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from web52103.mail.re2.yahoo.com (web52103.mail.re2.yahoo.com [206.190.48.106]) by postgresql.org (Postfix) with SMTP id F2FFC9FB1CC for ; Sat, 9 Jun 2007 18:15:11 -0300 (ADT) Received: (qmail 71455 invoked by uid 60001); 9 Jun 2007 21:07:48 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=0uW2kDoxaxyKBS5aWOpwlNon7Wj8GwVmKF7r0F1WItApeCeXQr3DLJL5yWkBByJ8sDjQWiIuIu7d35N3ihRwt6FhGA9OxbwSzSc7hIITom+HWnWSRzJLAZ9Ojpap7MOMEWpORPqRcBUjjsYj9BirjrC/u1muV9MACHvnT8bsu2g=; X-YMail-OSG: GczcPacVM1kaQE8cAUervqE2fZ6EikWh_wYG4Gn9ap0vRxaN3xGMZRoqaV30UZi4h7EW.O0MK8hgxiccnVgaR7GDIxMHmPneG0wNWuAFMb5eq_gtWaoAbIICV7qILHVgO9M9vlnfzyOXXyGs4TZoiVcFXw-- Received: from [74.222.221.248] by web52103.mail.re2.yahoo.com via HTTP; Sat, 09 Jun 2007 14:07:48 PDT X-Mailer: YahooMailRC/651.29 YahooMailWebService/0.7.41.16 Date: Sat, 9 Jun 2007 14:07:48 -0700 (PDT) From: flickchick_one Subject: Re: preload libraries To: Tom Lane Cc: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1063624777-1181423268=:70925" Message-ID: <451767.70925.qm@web52103.mail.re2.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.757 tagged_above=0 required=5 tests=BAYES_00=-2.599, DNS_FROM_RFC_ABUSE=0.2, DNS_FROM_RFC_POST=1.708, DNS_FROM_RFC_WHOIS=1.447, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200706/86 X-Sequence-Number: 25754 --0-1063624777-1181423268=:70925 Content-Type: text/plain; charset=ascii i've gone another direction on the issue, but am continuing to have problems with it. this time i've put my shared object file in the preferred location according to the pg_config command, then i'm attempting to create the function. i do have log output now, and am wondering if someone has an idea where to go with this. thanks in advance for your assistance. Log file output: STATEMENT: CREATE FUNCTION match(text, text) RETURNS BOOLEAN AS 'match.so', 'match' LANGUAGE 'C'; < - 2007-06-09 15:53:23 CDT>DEBUG: 00000: server process (PID 27181) was terminated by signal 11 < - 2007-06-09 15:53:23 CDT>LOCATION: LogChildExit, postmaster.c:2432 < - 2007-06-09 15:53:23 CDT>LOG: 00000: server process (PID 27181) was terminated by signal 11 < - 2007-06-09 15:53:23 CDT>LOCATION: LogChildExit, postmaster.c:2432 < - 2007-06-09 15:53:23 CDT>LOG: 00000: terminating any other active server processes < - 2007-06-09 15:53:23 CDT>LOCATION: HandleChildCrash, postmaster.c:2313 < - 2007-06-09 15:53:23 CDT>DEBUG: 00000: sending SIGQUIT to process 27168 < - 2007-06-09 15:53:23 CDT>LOCATION: HandleChildCrash, postmaster.c:2352 < - 2007-06-09 15:53:23 CDT>DEBUG: 00000: sending SIGQUIT to process 27154 < - 2007-06-09 15:53:23 CDT>LOCATION: HandleChildCrash, postmaster.c:2352 WARNING: 57P02: terminating connection because of crash of another server process DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. HINT: In a moment you should be able to reconnect to the database and repeat your command. LOCATION: quickdie, postgres.c:2118 < - 2007-06-09 15:53:23 CDT>DEBUG: 00000: sending SIGQUIT to process 27064 < - 2007-06-09 15:53:23 CDT>LOCATION: HandleChildCrash, postmaster.c:2366 < - 2007-06-09 15:53:23 CDT>DEBUG: 00000: sending SIGQUIT to process 27065 < - 2007-06-09 15:53:23 CDT>LOCATION: HandleChildCrash, postmaster.c:2400 < - 2007-06-09 15:53:23 CDT>DEBUG: 00000: server process (PID 27154) exited with exit code 1 < - 2007-06-09 15:53:23 CDT>LOCATION: LogChildExit, postmaster.c:2423 WARNING: 57P02: terminating connection because of crash of another server process DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. HINT: In a moment you should be able to reconnect to the database and repeat your command. LOCATION: quickdie, postgres.c:2118 < - 2007-06-09 15:53:23 CDT>DEBUG: 00000: server process (PID 27168) exited with exit code 1 < - 2007-06-09 15:53:23 CDT>LOCATION: LogChildExit, postmaster.c:2423 < - 2007-06-09 15:53:23 CDT>LOG: 00000: all server processes terminated; reinitializing < - 2007-06-09 15:53:23 CDT>LOCATION: reaper, postmaster.c:2213 < - 2007-06-09 15:53:23 CDT>LOG: 00000: database system was interrupted at 2007-06-09 15:52:43 CDT < - 2007-06-09 15:53:23 CDT>LOCATION: StartupXLOG, xlog.c:4373 < - 2007-06-09 15:53:23 CDT>LOG: 00000: checkpoint record is at 0/69E64C < - 2007-06-09 15:53:23 CDT>LOCATION: StartupXLOG, xlog.c:4441 < - 2007-06-09 15:53:23 CDT>LOG: 00000: redo record is at 0/69E64C; undo record is at 0/0; shutdown FALSE < - 2007-06-09 15:53:23 CDT>LOCATION: StartupXLOG, xlog.c:4468 < - 2007-06-09 15:53:23 CDT>LOG: 00000: next transaction ID: 2795; next OID: 57344 < - 2007-06-09 15:53:23 CDT>LOCATION: StartupXLOG, xlog.c:4471 < - 2007-06-09 15:53:23 CDT>LOG: 00000: next MultiXactId: 1; next MultiXactOffset: 0 < - 2007-06-09 15:53:23 CDT>LOCATION: StartupXLOG, xlog.c:4474 < - 2007-06-09 15:53:23 CDT>LOG: 00000: database system was not properly shut down; automatic recovery in progress < - 2007-06-09 15:53:23 CDT>LOCATION: StartupXLOG, xlog.c:4531 < - 2007-06-09 15:53:23 CDT>LOG: 00000: redo starts at 0/69E690 < - 2007-06-09 15:53:23 CDT>LOCATION: StartupXLOG, xlog.c:4568 < - 2007-06-09 15:53:23 CDT>LOG: 00000: record with zero length at 0/710054 < - 2007-06-09 15:53:23 CDT>LOCATION: ReadRecord, xlog.c:2763 < - 2007-06-09 15:53:23 CDT>LOG: 00000: redo done at 0/71002C < - 2007-06-09 15:53:23 CDT>LOCATION: StartupXLOG, xlog.c:4626 < - 2007-06-09 15:53:23 CDT>LOG: 00000: database system is ready < - 2007-06-09 15:53:23 CDT>LOCATION: StartupXLOG, xlog.c:4820 < - 2007-06-09 15:53:23 CDT>LOG: 00000: transaction ID wrap limit is 2147484146, limited by database "postgres" < - 2007-06-09 15:53:23 CDT>LOCATION: SetTransactionIdLimit, varsup.c:234 ----- Original Message ---- From: Tom Lane To: flickchick_one Cc: pgsql-admin@postgresql.org Sent: Tuesday, May 22, 2007 12:43:03 PM Subject: Re: [ADMIN] preload libraries flickchick_one writes: > I'm attempting to preload a shared object file (match.so) in order to create a C function in postgres that use will use it. To do this, I've added the following line to the postgresql.conf file: > preload_libraries = '/etc/postgresql/8.1/main/match.so' > Now when attempting to start the server, I receive the following error message: > Postgresql server failed to start. Please check the log output: > Although the message says to check the log for additional info, and a log is created for the event, the file is empty. The error message is most likely going to postmaster's stderr, which might or might not be captured by whatever logging setup you're using. Try starting the postmaster "by hand", ie just "postmaster -D wherever", and see if you get anything useful. It sounds like it's probably an object-file compatibility problem, but need the message to guess exactly what... regards, tom lane ____________________________________________________________________________________ Pinpoint customers who are looking for what you sell. http://searchmarketing.yahoo.com/ --0-1063624777-1181423268=:70925 Content-Type: text/html; charset=ascii
i've gone another direction on the issue, but am continuing to have problems with it.  this time i've put my shared object file in the preferred location according to the pg_config command, then i'm attempting to create the function.  i do have log output now, and am wondering if someone has an idea where to go with this.  thanks in advance for your assistance.

Log file output:

<postgres - 2007-06-09 15:53:23 CDT>STATEMENT:  CREATE FUNCTION match(text, text) RETURNS BOOLEAN
        AS 'match.so', 'match'
        LANGUAGE 'C';
< - 2007-06-09 15:53:23 CDT>DEBUG:  00000: server process (PID 27181) was terminated by signal 11
< - 2007-06-09 15:53:23 CDT>LOCATION:  LogChildExit, postmaster.c:2432
< - 2007-06-09 15:53:23 CDT>LOG:  00000: server process (PID 27181) was terminated by signal 11
< - 2007-06-09 15:53:23 CDT>LOCATION:  LogChildExit, postmaster.c:2432
< - 2007-06-09 15:53:23 CDT>LOG:  00000: terminating any other active server processes
< - 2007-06-09 15:53:23 CDT>LOCATION:  HandleChildCrash, postmaster.c:2313
< - 2007-06-09 15:53:23 CDT>DEBUG:  00000: sending SIGQUIT to process 27168
< - 2007-06-09 15:53:23 CDT>LOCATION:  HandleChildCrash, postmaster.c:2352
< - 2007-06-09 15:53:23 CDT>DEBUG:  00000: sending SIGQUIT to process 27154
< - 2007-06-09 15:53:23 CDT>LOCATION:  HandleChildCrash, postmaster.c:2352
<postgres - 2007-06-09 15:53:23 CDT>WARNING:  57P02: terminating connection because of crash of another server process
<postgres - 2007-06-09 15:53:23 CDT>DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
<postgres - 2007-06-09 15:53:23 CDT>HINT:  In a moment you should be able to reconnect to the database and repeat your command.
<postgres - 2007-06-09 15:53:23 CDT>LOCATION:  quickdie, postgres.c:2118
< - 2007-06-09 15:53:23 CDT>DEBUG:  00000: sending SIGQUIT to process 27064
< - 2007-06-09 15:53:23 CDT>LOCATION:  HandleChildCrash, postmaster.c:2366
< - 2007-06-09 15:53:23 CDT>DEBUG:  00000: sending SIGQUIT to process 27065
< - 2007-06-09 15:53:23 CDT>LOCATION:  HandleChildCrash, postmaster.c:2400
< - 2007-06-09 15:53:23 CDT>DEBUG:  00000: server process (PID 27154) exited with exit code 1
< - 2007-06-09 15:53:23 CDT>LOCATION:  LogChildExit, postmaster.c:2423
<postgres - 2007-06-09 15:53:23 CDT>WARNING:  57P02: terminating connection because of crash of another server process
<postgres - 2007-06-09 15:53:23 CDT>DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
<postgres - 2007-06-09 15:53:23 CDT>HINT:  In a moment you should be able to reconnect to the database and repeat your command.
<postgres - 2007-06-09 15:53:23 CDT>LOCATION:  quickdie, postgres.c:2118
< - 2007-06-09 15:53:23 CDT>DEBUG:  00000: server process (PID 27168) exited with exit code 1
< - 2007-06-09 15:53:23 CDT>LOCATION:  LogChildExit, postmaster.c:2423
< - 2007-06-09 15:53:23 CDT>LOG:  00000: all server processes terminated; reinitializing
< - 2007-06-09 15:53:23 CDT>LOCATION:  reaper, postmaster.c:2213
< - 2007-06-09 15:53:23 CDT>LOG:  00000: database system was interrupted at 2007-06-09 15:52:43 CDT
< - 2007-06-09 15:53:23 CDT>LOCATION:  StartupXLOG, xlog.c:4373
< - 2007-06-09 15:53:23 CDT>LOG:  00000: checkpoint record is at 0/69E64C
< - 2007-06-09 15:53:23 CDT>LOCATION:  StartupXLOG, xlog.c:4441
< - 2007-06-09 15:53:23 CDT>LOG:  00000: redo record is at 0/69E64C; undo record is at 0/0; shutdown FALSE
< - 2007-06-09 15:53:23 CDT>LOCATION:  StartupXLOG, xlog.c:4468
< - 2007-06-09 15:53:23 CDT>LOG:  00000: next transaction ID: 2795; next OID: 57344
< - 2007-06-09 15:53:23 CDT>LOCATION:  StartupXLOG, xlog.c:4471
< - 2007-06-09 15:53:23 CDT>LOG:  00000: next MultiXactId: 1; next MultiXactOffset: 0
< - 2007-06-09 15:53:23 CDT>LOCATION:  StartupXLOG, xlog.c:4474
< - 2007-06-09 15:53:23 CDT>LOG:  00000: database system was not properly shut down; automatic recovery in progress
< - 2007-06-09 15:53:23 CDT>LOCATION:  StartupXLOG, xlog.c:4531
< - 2007-06-09 15:53:23 CDT>LOG:  00000: redo starts at 0/69E690
< - 2007-06-09 15:53:23 CDT>LOCATION:  StartupXLOG, xlog.c:4568
< - 2007-06-09 15:53:23 CDT>LOG:  00000: record with zero length at 0/710054
< - 2007-06-09 15:53:23 CDT>LOCATION:  ReadRecord, xlog.c:2763
< - 2007-06-09 15:53:23 CDT>LOG:  00000: redo done at 0/71002C
< - 2007-06-09 15:53:23 CDT>LOCATION:  StartupXLOG, xlog.c:4626
< - 2007-06-09 15:53:23 CDT>LOG:  00000: database system is ready
< - 2007-06-09 15:53:23 CDT>LOCATION:  StartupXLOG, xlog.c:4820
< - 2007-06-09 15:53:23 CDT>LOG:  00000: transaction ID wrap limit is 2147484146, limited by database "postgres"
< - 2007-06-09 15:53:23 CDT>LOCATION:  SetTransactionIdLimit, varsup.c:234


----- Original Message ----
From: Tom Lane <tgl@sss.pgh.pa.us>
To: flickchick_one <flickchick_one@yahoo.com>
Cc: pgsql-admin@postgresql.org
Sent: Tuesday, May 22, 2007 12:43:03 PM
Subject: Re: [ADMIN] preload libraries

flickchick_one <flickchick_one@yahoo.com> writes:
>   I'm attempting to preload a shared object file (match.so) in order to create a C function in postgres that use will use it.  To do this, I've added the following line to the postgresql.conf file:
  
>   preload_libraries = '/etc/postgresql/8.1/main/match.so'
  
>   Now when attempting to start the server, I receive the following error message:
  
>   Postgresql server failed to start.  Please check the log output:
  
>   Although the message says to check the log for additional info, and a log is created for the event, the file is empty.

The error message is most likely going to postmaster's stderr, which
might or might not be captured by whatever logging setup you're using.
Try starting the postmaster "by hand", ie just "postmaster -D wherever",
and see if you get anything useful.

It sounds like it's probably an object-file compatibility problem, but
need the message to guess exactly what...

            regards, tom lane



Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. --0-1063624777-1181423268=:70925--