Hi List,
how to speedup nested loop queries and by which parameters.
--
Regards
Gauri
On Friday 23 March 2007 14:32, Matt Smiley wrote:
Thanks Dimitri! That was very educational material! I'm going to think
out loud here, so please correct me if you see any errors.
Your mail is so long - I was unable to answer all questions same day :))
The section on tuning for OLTP
On Mon, Mar 26, 2007 at 05:34:39PM +0530, Gauri Kanekar wrote:
how to speedup nested loop queries and by which parameters.
Please post a query you're trying to tune and the EXPLAIN ANALYZE
output, as well as any changes you've already made in postgresql.conf
or configuration variables you've set
Sorry,
this are the Confg Setting
max_connections = 100 # (change requires restart)
shared_buffers = 300MB
work_mem = 256MB
max_fsm_pages = 40
max_fsm_relations = 500
wal_buffers = 512
checkpoint_segments = 20
checkpoint_timeout = 900
enable_bitmapscan = on
enable_seqscan =
-Original Message-
From: [EMAIL PROTECTED] On Behalf Of Gauri Kanekar
Subject: Re: [PERFORM] Nested Loop
join_collapse_limit = 1 # JOINs
Is there a reason you have this set to 1? Postgres can't consider multiple
join orders when you do that. I would try setting that
On mán, 2007-03-26 at 20:33 +0530, Gauri Kanekar wrote:
you did not show your query, nor did you answer whather you had vacuumed
and analyzed.
enable_seqscan = off
why this? this is unlikely to help
QUERY PLAN
...
- Nested Loop
(cost=0.00..1104714.83
Sorin N. Ciolofan [EMAIL PROTECTED] writes:
I have to manage an application written in java which call another module
written in java which uses Postgre DBMS in a Linux environment. I'm new to
Postgres. The problem is that for large amounts of data the application
throws an:
