Kenneth Downs <[EMAIL PROTECTED]> 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

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

Reply via email to