From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andy <angelflow(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgresql's table & index compared to that of MySQL |
Date: | 2010-08-17 12:45:21 |
Message-ID: | AANLkTim68zqV_=HX32ztivLC7e1rj0pu+e-6xqTNYN0q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 17 August 2010 04:05, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andy <angelflow(at)yahoo(dot)com> writes:
>> Your results of 867MB for Postgresql & 3,576 MB for InnoDB are surprising. Do you know why it is so much smaller for Postgresql? Are there any indexes?
>
> If I understood the original report correctly, they were complaining
> mostly about index size, so a table without indexes certainly isn't
> a real helpful comparison.
Yeah, I did attempt to create a full text GIN index on that last
night, but it was taking ages and it was getting late, so abandoned
it. If you're interested, I set up one on MySQL's version (MyISAM of
course) and it was around 108 MB. The problem is, if PostgreSQL's
index was, say, 600 MB, it might still not be fair to compare it since
they make not really be equivalent.
But those slides leave a lot of important information out. And even
if it clearly explained everything in detail, they're talking about
7.4 and 8.0. The world has changed since then.
--
Thom Brown
Registered Linux user: #516935
From | Date | Subject | |
---|---|---|---|
Next Message | Ray Stell | 2010-08-17 13:02:57 | Re: How to do hot backup using postgres |
Previous Message | Boszormenyi Zoltan | 2010-08-17 12:29:16 | Re: How to refer to computed columns from other computed columns? |