Re: regproc's lack of certainty is dangerous - Mailing list pgsql-hackers

From Joe Conway
Subject Re: regproc's lack of certainty is dangerous
Date
Msg-id 3E6FAED7.1020107@joeconway.com
Whole thread Raw
In response to regproc's lack of certainty is dangerous  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: regproc's lack of certainty is dangerous
List pgsql-hackers
Tom Lane wrote:
> Another approach is to try to fix pg_statistic to avoid the problem by
> not doing I/O conversions.  For scalar datatypes (those that have
> associated array types) it'd be probably be feasible to store the
> histogram and most-common-value arrays as arrays of the datatype itself,
> not arrays of text; that should be a win for performance as well as
> avoiding risky conversions.  I am not sure what to do about columns that
> have datatypes without matching array types, though (that would include
> array columns and domains, IIRC).  Maybe use array of bytea to hold the
> internal representation of the type?

ISTM that the best (if not the only feasible) approach is using array of 
bytea to hold the internal representation of the type.

Joe




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: regproc's lack of certainty is dangerous
Next
From: Tom Lane
Date:
Subject: Re: regproc's lack of certainty is dangerous