Re: pageinspect: Hash index support - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pageinspect: Hash index support
Date
Msg-id c982b01c-06bc-485b-5dde-057ee244261a@2ndquadrant.com
Whole thread Raw
In response to Re: pageinspect: Hash index support  (Jesper Pedersen <jesper.pedersen@redhat.com>)
Responses Re: pageinspect: Hash index support
Re: pageinspect: Hash index support
List pgsql-hackers
On 9/26/16 1:39 PM, Jesper Pedersen wrote:
> Left as is, since BuildTupleFromCStrings() vs. xyzGetDatum() are equally 
> readable in this case. But, I can change the patch if needed.

The point is that to use BuildTupleFromCStrings() you need to convert
numbers to strings, and then they are converted back.  This is not a
typical way to write row-returning functions.

>> - hash_metap result fields spares and mapp should be arrays of integer.
> 
> B-tree and BRIN uses a 'text' field as output, so left as is.

These fields are specific to hash, so the precedent doesn't necessarily
apply.

>> - The data field could be of type bytea.
> 
> Left as is, for same reasons as 'spares' and 'mapp'.

Comments from others here?  Why not use bytea instead of text?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pg_basebackup, pg_receivexlog and data durability (was: silent data loss with ext4 / all current versions)
Next
From: Etsuro Fujita
Date:
Subject: Re: Push down more full joins in postgres_fdw