| From: | Kenneth Downs <ken(at)secdat(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | RPK <rpk(dot)general(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: MVCC cons |
| Date: | 2007-08-14 19:34:51 |
| Message-ID: | 46C203DB.7030605@secdat.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
> Kenneth Downs <ken(at)secdat(dot)com> writes:
>
>> Speaking as an end-user, I can give only one I've ever seen, which is
>> performance. Because of MVCC, Postgres's write performance (insert and
>> update) appears on my systems to be almost exactly linear to row size.
>> Inserting 1000 rows into a table with row size 100 characters takes
>> twice as long as inserting 1000 rows into a table with row size 50
>> characters.
>>
>
> Not sure why you'd think that's specific to MVCC. It sounds like purely
> an issue of disk write bandwidth.
>
> regards, tom lane
>
I did not see this in MS SQL Server.
--
Kenneth Downs
Secure Data Software, Inc.
www.secdat.com www.andromeda-project.org
631-689-7200 Fax: 631-689-0527
cell: 631-379-0010
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phoenix Kiula | 2007-08-14 19:35:01 | Compound Indexes |
| Previous Message | Tom Lane | 2007-08-14 19:30:47 | Re: MVCC cons |