| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: regproc's lack of certainty is dangerous |
| Date: | 2003-03-12 22:04:07 |
| Message-ID: | 3E6FAED7.1020107@joeconway.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-03-12 23:03:56 | Re: regproc's lack of certainty is dangerous |
| Previous Message | Tom Lane | 2003-03-12 20:16:29 | regproc's lack of certainty is dangerous |