Re: New pg_lsn type doesn't have hash/btree opclasses - Mailing list pgsql-hackers

From Fabrízio de Royes Mello
Subject Re: New pg_lsn type doesn't have hash/btree opclasses
Date
Msg-id CAFcNs+qA+_xrB31VuSPCMfLfEk3PrOf1aTrpdu_RV6qx4sMPXg@mail.gmail.com
Whole thread Raw
In response to Re: New pg_lsn type doesn't have hash/btree opclasses  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: New pg_lsn type doesn't have hash/btree opclasses  (Andres Freund <andres@2ndquadrant.com>)
Re: New pg_lsn type doesn't have hash/btree opclasses  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers

On Tue, May 6, 2014 at 8:25 PM, Michael Paquier <michael.paquier@gmail.com> wrote:
>
> On Wed, May 7, 2014 at 8:22 AM, Andres Freund <andres@2ndquadrant.com> wrote:
> > Uh. They're different:
> >
> > Datum
> > timestamp_hash(PG_FUNCTION_ARGS)
> > {
> >         /* We can use either hashint8 or hashfloat8 directly */
> > #ifdef HAVE_INT64_TIMESTAMP
> >         return hashint8(fcinfo);
> > #else
> >         return hashfloat8(fcinfo);
> > #endif
> > }
> > note it's passing fcinfo, not the datum as you do. Same with
> > time_hash.. In fact your version crashes when used because it's
> > dereferencing a int8 as a pointer inside hashfloat8.
> Thanks, didn't notice that fcinfo was used.
>

Hi all,

If helps, I added some regression tests to the lastest patch.

Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: need xmllint on borka
Next
From: Tom Lane
Date:
Subject: Schizophrenic coding in gin_extract_jsonb(_hash)