"Andreas 'ads' Scherbaum" writes:
> The patch changes the benchmark tool in a way that the explain output is
> printed to standard out - what one would expect from the "-e" (explain)
> option.
> The new status of this patch is: Ready for Committer
Pushed, thanks.
regar
The following review has been posted through the commitfest application:
make installcheck-world: not tested
Implements feature: not tested
Spec compliant: not tested
Documentation:not tested
The patch changes the benchmark tool in a way that the explain output is
pri
In the contrib/intarray benchmarking script bench.pl, the -e option to print
the plan via EXPLAIN is using the DBI do() method which discards output
resulting in nothing being printed. Judging by the usage help (“show explain”)
I assume the intention is to print the plan to STDOUT when invoked (wh
On Thu, 2012-02-16 at 19:27 -0500, Tom Lane wrote:
> Guillaume Lelarge writes:
> > This query:
> > SELECT ARRAY[-1,3,1] & ARRAY[1, 2];
> > should give {1} as a result.
>
> > But, on HEAD (and according to his tests, on 9.0.6 and 9.1.2), it
> > appears to give en empty array.
>
> Definitely a b
Guillaume Lelarge writes:
> This query:
> SELECT ARRAY[-1,3,1] & ARRAY[1, 2];
> should give {1} as a result.
> But, on HEAD (and according to his tests, on 9.0.6 and 9.1.2), it
> appears to give en empty array.
Definitely a bug, and I'll bet it goes all the way back.
> Digging on this issue,
Hi,
On a french PostgreSQL web forum, one of our users asked about a curious
behaviour of the intarray extension.
This query:
SELECT ARRAY[-1,3,1] & ARRAY[1, 2];
should give {1} as a result.
But, on HEAD (and according to his tests, on 9.0.6 and 9.1.2), it
appears to give en empty array.
Digg
