From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Mario Weilguni <mweilguni(at)sime(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Crash in pgCrypto? |
Date: | 2008-06-16 13:54:16 |
Message-ID: | 20080616135416.GD4325@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Mario Weilguni wrote:
> Could someone using the pgcrypto extension please verify this?
>
> SELECT encode(digest(null, 'md5'::text), 'hex');
> or
> SELECT digest(null, 'md5');
>
> Takes a few seconds, and then crashes the server with a Signal 11. My
> system is PostgreSQL 8.2.7. Seems to be an unchecked access to memory
> location 0.
I think the functions were made STRICT recently, and the NULL checks
were removed, but people with the old definitions of the functions could
see the crashes. Try removing pgcrypto and recompiling it from a fresh
release.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2008-06-16 14:24:41 | Re: Question about Encoding a Custom Type |
Previous Message | Mario Weilguni | 2008-06-16 13:03:34 | Re: Crash in pgCrypto? |