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-06 13:15:47
Message-ID: e51f66da0711060515h659c62cfk1ffe4ef7d0d45e00@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/6/07, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Alvaro Herrera wrote:
> > > > Tom, how about putting a note about that into next 8.2 minor
> > > > release notes? (8.3 too?) Something like "You need to refresh
> > > > pgcrypto functions, because since rel 8.2 the code depends
> > > > on functions being tagged STRICT."
> > >
> > > Seems 8.2.5 was released without this release notes mention, but we
> > > haven't gotten any complaints about it so perhaps we don't need to add
> > > anything.
> >
> > Huh, I see exactly that complaint above.
>
> My point is that we can't mention it in the release notes until 8.2.6.
> Will there still be people who are having an issue with it who haven't
> found the problem already? And if we put it in 8.2.6, it really was
> effective for 8.2 so we just mention it in 8.2.6 and say it applies to
> 8.2.X too?

We know that only few people have found the problem, because
there is no way for them to guess what the fix should be
by themselves, without consulting postgres lists.

And I suspect most of the people who have not found out about
the bug would still like to fix it in their setup, as crashing
database is not fun. If only they knew about the problem...

--
marko

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Kreen 2007-11-06 13:17:05 Re: Visibility map thoughts
Previous Message Simon Riggs 2007-11-06 13:15:02 Re: Test lab