From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Shelby Cain <alyandon(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: select statement against pg_stats returns inconsistent |
Date: | 2004-02-25 00:38:31 |
Message-ID: | 403BEE87.20703@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Tom Lane wrote:
> Hoo, I'm surprised no one noticed this during 7.4 development/testing.
> The problem applies for any datatype that requires double alignment,
> which includes int8, float8, and timestamp as well as most of the
> geometric types. pg_statistic is declared as using type "anyarray",
> and this type really needs to be marked as requiring double alignment
> so that arrays of double-aligned datatypes will come out correctly.
anyarray has been defined this way since 7.3 -- any concerns there? I
see that back then pg_statistic used text[] instead of anyarray, so
perhaps not.
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Goodwin | 2004-02-25 02:15:11 | Re: Inheritance and column references problem |
Previous Message | Stephan Szabo | 2004-02-25 00:38:28 | Re: Inheritance and column references problem |
From | Date | Subject | |
---|---|---|---|
Next Message | Dann Corbit | 2004-02-25 00:50:23 | Re: Is indexing broken for bigint columns? |
Previous Message | Mike Mascari | 2004-02-25 00:37:14 | Re: Is indexing broken for bigint columns? |