From: Ken Egervari <ken@upfactor.com>
To: pgsql-performance@postgresql.org
Subject: Re: Help with tuning this query
Date: Wed, 2 Mar 2005 13:56:57 -0500
Message-ID: <002801c51f59$9c043900$6a01a8c0@KEN> (raw)
References: <001001c51ef4$3849eeb0$6a01a8c0@KEN>
<1109787227.31084.12.camel@localhost.localdomain>
<000901c51f55$aa4b7400$6a01a8c0@KEN>
<1109789394.31084.20.camel@localhost.localdomain>
>> left join is for eager loading so that I don't have to run a seperate
>> query
>> to fetch the children for each shipment. This really does improve
>> performance because otherwise you'll have to make N+1 queries to the
>> database, and that's just too much overhead.
>
> are you saying that you are actually doing a
> select s.*,ss.* ...
> ?
Yes, this is how the SQL should be written. When I manually converted the
query, I forgot to include this detail. In hibernate, you don't need to
specifiy the ss.* because you are dealing with objects, so you just say
shipment. The ss.* is indicated in the "fetch" part of the Hibernate query.
That was my mistake.
> it might help the planner estimate better the number of cs rows
> affected. whether this improves performance depends on whether
> the best plans are sensitive to this.
This sounds like a good idea since cs rows are quite large. shipment and
shipment_status are the largest tables in the database and they will grow
very large over time.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ken@upfactor.com
Subject: Re: Help with tuning this query
In-Reply-To: <002801c51f59$9c043900$6a01a8c0@KEN>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox