pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andrew Biagioni <andrew.biagioni@e-greek.net>
To: Juan Miguel <juanmime@ono.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Speed & Memory Management
Date: Wed, 02 Apr 2003 17:24:22 -0500
Message-ID: <3E8B6316.6080505@e-greek.net> (raw)
In-Reply-To: <200304022313.17633.juanmime@ono.com>
References: <200304022313.17633.juanmime@ono.com>



Juan Miguel wrote:

>>That would buy you absolutely nothing.  char() is not faster than text.
>>Instead you would make everything slower because the system would
>>constantly have to pad and trim your values and it would bloat the storage
>>with the extra spaces.
>>    
>>
>
>First, sorry about my english.
>
>Well ... but ... reading database theory books, you can see that fixed size 
>records are "better" than variant size records. When the records are size 
>fixed,  inserts, updates and deletes can recalculate easier the position of 
>the rest records in the pages. These books tell you that in general cases, 
>variant record size tables (records that have variant type colums, for 
>example) imply a lower performance in the system ...
>
>Why in postgresql these things don't matter ?
>  
>
Because unlike other DBs, PostgreSQL doesn't actually remove anything 
when you do an update or delete, it marks the old record as "dead" and 
(for an update) adds a new instance of the record at the end.  That's 
one reason why you want to vacuum tables after some activity, to remove 
the dead records fro all updates/deletes.

>Thanks.
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 3: if posting/reading through Usenet, please send an appropriate
>subscribe-nomail command to majordomo@postgresql.org so that your
>message can get through to the mailing list cleanly
>
>
>  
>

view thread (14+ messages)  latest in thread

Message-ID: <3E8B6316.6080505@e-greek.net>
Permalink:  ../3E8B6316.6080505@e-greek.net/
Also on:    postgresql.org/message-id/3E8B6316.6080505@e-greek.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: andrew.biagioni@e-greek.net, juanmime@ono.com
  Subject: Re: Speed & Memory Management
  In-Reply-To: <3E8B6316.6080505@e-greek.net>
  References: <200304022313.17633.juanmime@ono.com> <3E8B6316.6080505@e-greek.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox