PostgreSQL 7.3.3 with pgcrypto on FreeBSD 5.1 - Mailing list pgsql-bugs

From Alex Rodin
Subject PostgreSQL 7.3.3 with pgcrypto on FreeBSD 5.1
Date
Msg-id 3F1BC628.4020907@sm.ukrtel.net
Whole thread Raw
Responses Re: PostgreSQL 7.3.3 with pgcrypto on FreeBSD 5.1
List pgsql-bugs
============================================================================
                        POSTGRESQL BUG REPORT TEMPLATE
============================================================================


Your name        :    Alexey Rodin
Your email address    :    alx@sm.ukrtel.net


System Configuration
---------------------
  Architecture       : CPU: AMD Duron(tm) processor (801.42-MHz 686-class CPU)

  Operating System      : FreeBSD 5.1-RELEASE

  PostgreSQL version     : PostgreSQL-7.3.3

  Compiler used     : gcc version 3.2.2 [FreeBSD] 20030205 (release)


Please enter a FULL description of your problem:
------------------------------------------------

PostgreSQL 7.3.3 with pgcrypto crushed after execute test sql query.



Please describe a way to repeat the problem.   Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------

testdb=# SELECT crypt('lalalal',gen_salt('md5'));

    server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
    The connection to the server was lost. Attempting reset: Failed.

<pglog>

LOG:  ReadRecord: record with zero length at 0/18BDEA8
LOG:  redo is not required
LOG:  database system is ready
LOG:  server process (pid 21460) was terminated by signal 11
LOG:  terminating any other active server processes
LOG:  all server processes terminated; reinitializing shared memory and semaphores
LOG:  database system was interrupted at 2003-07-21 11:44:47 EEST
LOG:  checkpoint record is at 0/18BDEA8
LOG:  redo record is at 0/18BDEA8; undo record is at 0/0; shutdown TRUE
LOG:  next transaction id: 996; next oid: 98896
LOG:  database system was not properly shut down; automatic recovery in progress
FATAL:  The database system is starting up


</pglog>

If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: deadlock_timeout and pg_ctl reload
Next
From: DeJuan Jackson
Date:
Subject: Re: [GENERAL] INSTEAD rule bug?