I run on PostgreSQL 8.3, default settings (also tried to change
random_page_cost close to 1).
What need I change to make the second query run as fast as the first?
Set enable_hashjoin to off solves this problem, but it's not the way I
can use.
Statistics for all columns is on the level 1000.
e
PFC пишет:
On Thu, 24 Apr 2008 03:14:54 +0200, Vlad Arkhipov
<[EMAIL PROTECTED]> wrote:
I found strange issue in very simple query. Statistics for all columns
is on the level 1000 but I also tried other levels.
create table g (
id bigint primary key,
isgroup boolean not null);
create tab
Hi,
using this strategy to study the overhead of EXPLAIN ANALYZE was very
insightful. Apparently, measuring the performance of the query plan
introduced a overhead of more than 10 seconds in the query I was
looking at.
Thanks,
Viktor
Am 24.04.2008 um 19:05 schrieb PFC:
Do you mean, that
(thread crossed over to pgsql-performance, where it belongs, from
pgsql-advocacy)
Greg,
I think TPC-E will make both of these major improvements much more important.
I suspect it would be hard to get 8.2 to even pass TPC-E due to the checkpoint
dropouts.
You'd be surprised, then. We're sti
On Sat, 26 Apr 2008, Adonias Malosso wrote:
The current approach is to dump the data in CSV and than COPY it to
Postgresql.
You would have to comment on what you don't like about what you're doing
now, what parts need to be improved for your priorities, to get a properly
targeted answer here
