From: | Lincoln Yeoh <lylyeoh(at)mecomb(dot)com> |
---|---|
To: | Vadim Mikheev <vadim(at)krs(dot)ru> |
Cc: | Charles Tassell <ctassell(at)isn(dot)net>, pgsql-general(at)postgreSQL(dot)org |
Subject: | Re: [GENERAL] Postgres INSERTs much slower than MySQL? |
Date: | 1999-10-20 08:33:18 |
Message-ID: | 3.0.5.32.19991020163318.0087e140@pop.mecomb.po.my |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
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.
How many rows (blocks) can I insert before I have to do a commit?
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.
But to fix the resulting problem I had to manually rm the files related to
the table. I also dropped the database to make sure ;). That's not good.
Cheerio,
Link.
From | Date | Subject | |
---|---|---|---|
Next Message | Vadim Mikheev | 1999-10-20 08:38:09 | Re: [GENERAL] Postgres INSERTs much slower than MySQL? |
Previous Message | Vadim Mikheev | 1999-10-20 08:12:50 | Re: [GENERAL] Postgres INSERTs much slower than MySQL? |
From | Date | Subject | |
---|---|---|---|
Next Message | Vadim Mikheev | 1999-10-20 08:38:09 | Re: [GENERAL] Postgres INSERTs much slower than MySQL? |
Previous Message | Vadim Mikheev | 1999-10-20 08:12:50 | Re: [GENERAL] Postgres INSERTs much slower than MySQL? |