OK, can you attach to the running process and tell us what functions it
is running. That would help.
[Charset iso-8859-2 unsupported, filtering to ASCII...]
> Hi,
>
> recently I tried to reproduce some benchmark results
> when I discovered a very strange behavior. I did
> my tests with the current snapshot of last week,
> but other people who have performed the same bench-
> mark with postgresql-6.4-2 reported the same problems.
>
> The setup is pretty simple: one table with 13
> integer and 7 char(20) columns. For every column
> an index is created. The postmaster is started with
> -o -F and before each query a 'vacuum analyze' is
> performed.
>
> When loading 100.000 rows into the table
> everything works ok. Selects and updates
> are reasonable fast. But when loading
> 1.000.000 rows the select statements still
> work, but a simple update statement
> shows this strange behavior. A never ending
> disk-activity starts. Memory consumption
> increases up to the physical limit (384 MB)
> whereas the postmaster uses only a few %
> of CPU time. After 1 hour I killed the post-
> master.
>
> It would be nice, if this could be fixed.
> People from the german UNIX magazine IX
> benchmarked Oracle, Informix and Sybase on Linux
> and they claimed, that Postgres is totally unusable
> because of this problem.
>
> If you need some additional info, just let me know.
>
>
> Edmund
>
>
> --
> Edmund Mergl mailto:E.Mergl@bawue.de
> Im Haldenhau 9 http://www.bawue.de/~mergl
> 70565 Stuttgart fon: +49 711 747503
> Germany
>
>
-- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026
