From: | Vadim Mikheev <vadim(at)krs(dot)ru> |
---|---|
To: | Lincoln Yeoh <lylyeoh(at)mecomb(dot)com> |
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:38:09 |
Message-ID: | 380D7F71.F422AEC4@krs.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general 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
From | Date | Subject | |
---|---|---|---|
Next Message | Fernando Schapachnik | 1999-10-20 13:55:49 | Neverending query on 6.5.0 over Solaris 2.5.1 SPARC |
Previous Message | Lincoln Yeoh | 1999-10-20 08:33:18 | Re: [GENERAL] Postgres INSERTs much slower than MySQL? |
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 1999-10-20 09:11:00 | enabling using index in ORDER BY ... desc |
Previous Message | Lincoln Yeoh | 1999-10-20 08:33:18 | Re: [GENERAL] Postgres INSERTs much slower than MySQL? |