> Hi Merlin,
>
> > The 9206 ms time is what the database actually spent
> > gathering the data and sending it to you. This is non-negotiable
unless
> you bump up
> > hardware, etc, or fetch less data. This time usually scales
linearly
> > (or close to it) with the size of the dataset you fetch.
Hi Merlin,
> The 9206 ms time is what the database actually spent
> gathering the data and sending it to you. This is non-negotiable unless you bump up
> hardware, etc, or fetch less data. This time usually scales linearly
> (or close to it) with the size of the dataset you fetch.
>
> The 40638
Joost wrote:
> My system is a PostgreSQL 7.4.1 on i686-pc-linux-gnu, compiled by GCC
gcc
> (GCC) 20020903 (Red Hat Linux 8.0 3.2-7). It has a Pentium III-733 Mhz
> with 512 MB ram. It is connected to my workststation (dual XEON 1700
with
> 1 Gb RAM) with a 100 Mb switched network.
>
> I have a tab
Hi all,
My system is a PostgreSQL 7.4.1 on i686-pc-linux-gnu, compiled by GCC gcc (GCC)
20020903 (Red Hat Linux 8.0 3.2-7). It has a Pentium III-733 Mhz with 512 MB ram. It
is connected to my workststation (dual XEON 1700 with 1 Gb RAM) with a 100 Mb switched
network.
I have a table with 31 co
