>
> It seems we need something like that too. I've just run the new perftest
> program against PostgreSQL and Oracle. It does:
>
> 1) insert 1407 tuples into two tables
> 2) select one attribute from one table
> 3) select one attribute from the join og both tables
> 4) updates one attribute in one table.
>
> Here are the results:
>
> Oracle:
> I needed 24 seconds and 1937 microseconds for the insert test.
> I needed 1 seconds and 600641 microseconds for the selection&projection test.
> I needed 1 seconds and 703673 microseconds for the join test.
> I needed 2 seconds and 404709 microseconds for the update test.
>
> PostgreSQL with -F:
> I needed 10 seconds and 297716 microseconds for the insert test.
> I needed 28 seconds and 964208 microseconds for the selection&projection test.
> I needed 83 seconds and 931762 microseconds for the join test.
> I needed 0 seconds and 588390 microseconds for the update test.
This seems strange. Is a vacuum being done so the optimizer knows how
large each table is?
--
Bruce Momjian | 830 Blythe Avenue
maillist@candle.pha.pa.us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)