Re: [GENERAL] Postgres INSERTs much slower than MySQL?
Vadim Mikheev <vadim@krs.ru>
From: Vadim Mikheev <vadim@krs.ru>
To: Lincoln Yeoh <lylyeoh@mecomb.com>
Cc: Charles Tassell <ctassell@isn.net>, pgsql-general@postgreSQL.org
Date: 1999-10-20T08:38:09Z
Lists: pgsql-hackers
Lincoln Yeoh wrote: > > At 04:12 PM 20-10-1999 +0800, Vadim Mikheev wrote: > >It doesn't seem as MVCC problem. MVCC uses transaction ids, > >not tuple ones, and so should work with any number of rows > >modified by concurrent transaction... In theory... -:)) > > OK. Dunno what I hit then. I wasn't modifying rows, I was inserting rows. You hit buffer manager/disk manager problems or eat all disk space. As for "modifying" - I meant insertion, deletion, update... > How many rows (blocks) can I insert before I have to do a commit? Each transaction can have up to 2^32 commands. > Well anyway the Postgres inserts aren't so much slower if I only commit > once in a while. Only about 3 times slower for the first 100,000 records. > So the subject line is now inaccurate :). Not bad, I like it. Hope that it will be much faster when WAL will be implemented... Vadim