From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andy <angelflow(at)yahoo(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgresql's table & index compared to that of MySQL |
Date: | 2010-08-16 23:47:54 |
Message-ID: | 25785.1282002474@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Andy <angelflow(at)yahoo(dot)com> writes:
> Are there any reasons why table & index sizes of Postgresql should be larger than MySQL?
Well, the per-row headers in PG are definitely bigger because of MVCC
requirements. It's hard to speculate much about index sizes with
no information about the table/index schemas.
> The company in the presentation used Postgresql 8.1. Has there been any significant changes in data size between 8.1 and 8.4/9.0?
Well, we shaved 4 bytes off the tuple header size since 8.1, and there's
been work on cutting per-field overhead too, and there's now some
ability to control fillfactor in indexes. But there's really not enough
information here to say how much difference this might've made for them.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-08-17 00:37:00 | Re: Postgresql's table & index compared to that of MySQL |
Previous Message | Andy | 2010-08-16 22:59:02 | Postgresql's table & index compared to that of MySQL |