I wrote:
> Dennis Noordsij writes:
>> What happens is [ integer overflow ]
> Doh ... so the increase in the maximum histogram size *is* related.
> Thanks, will fix.
Patch is here if you need it right away:
http://archives.postgresql.org/message-id/20090505180211.b2a59754...@cvs.postgresql.org
Dennis Noordsij writes:
> What happens is [ integer overflow ]
Doh ... so the increase in the maximum histogram size *is* related.
Thanks, will fix.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
h
On Tuesday 05 May 2009 17:16:03 Tom Lane wrote:
> "Dennis Noordsij" writes:
> > (gdb) bt
> > #0 0x004eecf7 in compute_scalar_stats (stats=0x1abd878,
> > fetchfunc=0x4f0f30 , samplerows= > out>, totalrows=4154315)
> > at analyze.c:2321
> > #1 0x004efbf5 in analyze_rel (rel
Tom Lane wrote:
"Dennis Noordsij" writes:
(gdb) bt
#0 0x004eecf7 in compute_scalar_stats (stats=0x1abd878,
fetchfunc=0x4f0f30 , samplerows=,
totalrows=4154315)
at analyze.c:2321
#1 0x004efbf5 in analyze_rel (relid=16484, vacstmt=0x1aaf140,
bstrategy=, update_reltup
"Dennis Noordsij" writes:
> (gdb) bt
> #0 0x004eecf7 in compute_scalar_stats (stats=0x1abd878,
> fetchfunc=0x4f0f30 , samplerows=,
> totalrows=4154315)
> at analyze.c:2321
> #1 0x004efbf5 in analyze_rel (relid=16484, vacstmt=0x1aaf140,
> bstrategy=, update_reltuples=1
