Re: Segmentation fault using digest from pg_crypto

From: "Marko Kreen" <markokr(at)gmail(dot)com>
To: "Bruce Momjian" <bruce(at)momjian(dot)us>
Cc: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Manuel Sugawara" <masm(at)fciencias(dot)unam(dot)mx>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Segmentation fault using digest from pg_crypto
Date: 2007-11-09 23:39:31
Message-ID: e51f66da0711091539v442fb332me0001c2620ceab10@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/7/07, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> OK, should we add a mention in the 8.2.6 release notes or put it in the
> 8. notes and figure if someone is upgrading they will read the 8.2
> notes? What would the description be?

"""
Note about pgcrypto - the functions were made STRICT in 8.1
and the NULL check was removed in 8.2 from C code. If some
database still contains non-STRICT signatures from 8.0 and below,
the functions will crash on NULL. To fix it the pgcrypto.sql
needs to be run that will re-create the signatures.
"""

Hm. Is there way to say that better?

--
marko

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-11-09 23:43:35 Re: Segmentation fault using digest from pg_crypto
Previous Message Tom Lane 2007-11-09 23:14:16 Re: Is "query" a reserved word in 8.3 plpgsql?