From: | "Greg Johnson" <greg(dot)johnson(at)interprose(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #5243: Segmentation fault when sending null to crypt(); |
Date: | 2009-12-14 18:20:07 |
Message-ID: | 200912141820.nBEIK7r7052104@wwwmaster.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 5243
Logged by: Greg Johnson
Email address: greg(dot)johnson(at)interprose(dot)com
PostgreSQL version: 8.4.1, 8.3.8
Operating system: CentOS 5.4
Description: Segmentation fault when sending null to crypt();
Details:
Postgresql version 8.4.1 and 8.3.8 both seg fault when you pass null into
crypt function.
select crypt(null, gen_salt('md5'));
Server Log
----------------------------
LOG: statement: select crypt(null, gen_salt('md5'));
LOG: server process (PID 25855) was terminated by signal 11: Segmentation
fault
LOG: terminating any other active server processes
FATAL: the database system is in recovery mode
WARNING: 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-12-14 18:40:13 | Re: BUG #5243: Segmentation fault when sending null to crypt(); |
Previous Message | Robert Haas | 2009-12-14 17:59:35 | Re: Invalid explain output for multi-plan statements |