--- Tom Lane <[EMAIL PROTECTED]> 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 decl
Dear Shelby Cain ,
Is this expected behavior or perhaps a bug?
For a novice like me can anyone please tell me
1. Will this effect my application developed on PostgreSQL
2. Will my Application break at some point I heavly use the type of
queries defined in the post.
Would be greatfull for
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> Has anyone given any thought as to whether dumping and restoring
> pg_statistic is worthwhile?
Why? You can reconstruct it with a simple "ANALYZE" command. Dumping
and restoring would mean nailing down cross-version assumptions about
what it
Joe Conway <[EMAIL PROTECTED]> writes:
> anyarray has been defined this way since 7.3 -- any concerns there?
I don't think so --- we weren't trying to use it as an actual column
datatype back then.
7.4 has a problem though :-( ... this is one of the "damn I wish we'd
caught that before release" o
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
Shelby Cain <[EMAIL PROTECTED]> writes:
> The select statements return different data for
> most_commons_vals depending on whether n_distinct is
> included in the select clause or not.
> I only seem to get the behavior below against int8
> columns - but I haven't interated through every
> conceivab
The select statements return different data for
most_commons_vals depending on whether n_distinct is
included in the select clause or not.
I only seem to get the behavior below against int8
columns - but I haven't interated through every
conceivable data type either.
Is this expected behavior or
