On Tue, 2005-03-15 at 12:18, Ragnar Hafstaà wrote:
> On Tue, 2005-03-15 at 18:10 +0100, Andreas Hartmann wrote:
>
> > explain analyze select * from veranstaltung_original order by semester;
> >
> > Sort (cost=3054.08..3067.74 rows=5467 width=223) (actual
> > time=2568.10..2573.02 rows=5467 lo
On Tue, 2005-03-15 at 18:10 +0100, Andreas Hartmann wrote:
> explain analyze select * from veranstaltung_original order by semester;
>
> Sort (cost=3054.08..3067.74 rows=5467 width=223) (actual
> time=2568.10..2573.02 rows=5467 loops=1)
> Sort Key: semester
> -> Seq Scan on veranstal
On Tue, 2005-03-15 at 11:10, Andreas Hartmann wrote:
> Hi all,
>
> I'm running the same database on two systems:
>
> A) Debian PostgreSQL 7.4.7
> B) SuSE PostgreSQL 7.3.4
>
> Both machines have approx. 1GHz and 1GB RAM.
> The amount of data is almost equal (+- 10%). But I'm facing
> huge perfo
Andreas Hartmann wrote:
Hi all,
I'm running the same database on two systems:
A) Debian PostgreSQL 7.4.7
B) SuSE PostgreSQL 7.3.4
Both machines have approx. 1GHz and 1GB RAM.
The amount of data is almost equal (+- 10%). But I'm facing
huge performance differences. For instance, a simple sequentia
Hi all,
I'm running the same database on two systems:
A) Debian PostgreSQL 7.4.7
B) SuSE PostgreSQL 7.3.4
Both machines have approx. 1GHz and 1GB RAM.
The amount of data is almost equal (+- 10%). But I'm facing
huge performance differences. For instance, a simple sequential
scan results in the fo
