From: Joe Shevland <shevlandj@kpi.com.au>
To: Francisco Jose Toledano Alcala <ftoledano@retemail.es>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Slow Recordset
Date: Sat, 06 May 2000 02:04:40 +1000
Message-ID: <3912F118.8C354300@kpi.com.au> (raw)
References: <3911DF11.4FBD054F@retemail.es>
<391209D6.3C3AD382@kpi.com.au>
<3912E30E.E910897B@retemail.es>
You could try a clustered index with the CLUSTER command, thoughs there's a few
things worth reading about it first. I don't know that this would really help in
this case though.
Joe
Francisco Jose Toledano Alcala wrote:
>
> Joe Shevland wrote:
> >
> > Francisco Jose Toledano Alcala wrote:
> > >
> > > Hello everyone.
> > >
> > > I think i've got a big problem developing an client-server aplication.
> > > On Server side I use a postgress sql server for linux, using SuSe 6.3
> > > distribution, all over a ethernet network with aproxmately 10 clients.
> > > On clients side, i use windows 98 and Visual Basic 6 clients programs
> > > using ADO throught odbc (postgress odbc driver).
> > >
> > > All run ok. I create a database and 5 tables on Access to export all
> > > throught odbc to Postgress Server. Export work ok, and all registers
> > > apears ok. The primary key is exported correctly too.
> > >
> > > The table has aproximately 15 fields with one of the of type 'text'.
> > >
> > > The i run on Visual a program to fill the database with 50.000 registers
> > > with ADO. All run ok, but when on client run a query like "select * from
> > > alumnos order by codalumno;" over all registers, the query spend aprox.
> > > 35 seconds. The server is a Pentium III, 128 Mb RAM, 8'4 UDMA 66 IDE
> > > disk.
> > >
> > > I think there must be an error on postmaster daemon runing because its
> > > imposible to run as slow as i see.
> > >
> > > Must optimize the database with a view or something like that?
> > > Is this normal?
> > > Need more indexes? (I've only the primary key)
> >
> > Is 'codalumno' the primary key? If not defining an index on this column
> > may speed things up.
> >
>
> Yes, it's primary key.
>
> > Can you execute the query on the server using 'psql' and compare
> > results?
> >
> Timing results are executed on server side throught psql.
--
Joe Shevland
Principal Consultant
KPI Logistics Pty Ltd
http://www.kpi.com.au
mailto:shevlandj@kpi.com.au
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-interfaces@postgresql.org
Cc: shevlandj@kpi.com.au, ftoledano@retemail.es
Subject: Re: Slow Recordset
In-Reply-To: <3912F118.8C354300@kpi.com.au>
* 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