Re: Segmentation fault using digest from pg_crypto

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Marko Kreen <markokr(at)gmail(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-05 22:12:37
Message-ID: 20071105221237.GK6511@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:
> Marko Kreen wrote:
> > On 8/24/07, Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx> wrote:

> > > If something is not going a work (or is going a work in a different
> > > way) in some version after loading a shot form a previous one I think
> > > it should be documented or some kind of backwards compatibility
> > > mechanism should be provided.
> >
> > That's a valid complaint and I take the blame.
> >
> > The problem was that such "evolution" was not actually planned.
> > So when I noticed the 8.2 commit, I did not think of the implications
> > hard enough to realize the need for release note for it.
> >
> > 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.

--
Alvaro Herrera http://www.amazon.com/gp/registry/5ZYLFMCVHXC
"Estoy de acuerdo contigo en que la verdad absoluta no existe...
El problema es que la mentira sí existe y tu estás mintiendo" (G. Lama)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-11-05 22:15:59 Re: Segmentation fault using digest from pg_crypto
Previous Message Rick Gigger 2007-11-05 22:01:12 Re: should I worry?