> The most efficient way to handle this query would probably be to join
> the three tables with restrictions first, and then join the other tables
> to those. You could force this with not too much rewriting using
> something like (untested, but I think it's right)
>
> ... FROM commercial_entity C
David Griffiths <[EMAIL PROTECTED]> writes:
> ... FROM commercial_entity, country, user_account,
> address_list LEFT JOIN state_province ON address_list.state_province_id
> = state_province.state_province_id
> LEFT JOIN contact_info ON address_list.contact_info_id =
> contact_info.contact_info_id
>
I continue struggling with the TPC-R benchmarks and wonder if anyone
could help me optimize the query below. ANALYZE statistics indicate that
the query should run relatively fast, but it takes hours to complete. I
attached the query plan to this posting.
Thanks.
select
nation,
o_ye
And finally,
Here's the contents of the postgresql.conf file
(I've been playing with these setting the last couple of days, and using the
guide @ http://www.varlena.com/varlena/GeneralBits/Tidbits/annotated_conf_e.html to
make sure I didn't have it mis-tuned):
tcpip_socket = truemax_conn
Here's the schema:
Table "public.address_list"
Column
|
Type |
Modifiers--++--- address_list_id
| numeric(10,0) | not
null address_1
| character varying(100)
|
We're having a problem with a query during our
investigation into Postgres (as an Oracle replacement). This query Postgres
takes 20-40 seconds (multiple runs). Tom Lan recommended I post it here, with an
explain-analyze.
Here's the query:
EXPLAIN ANALYZE SELECT company_name, address_1,
On Wed, 17 Sep 2003, Tom Lane wrote:
> Michael Adler <[EMAIL PROTECTED]> writes:
> > I have been experimenting with a new Seagate Cheetah 10k-RPM SCSI to
> > compare with a cheaper Seagate Barracuda 7200-RPM IDE (each in a
> > single-drive configuration). The Cheetah definately dominates the gene
