Re: WIP: extensible enums

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: WIP: extensible enums
Date: 2010-10-20 01:15:33
Message-ID: 4CBE42B5.6000908@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/19/2010 08:51 PM, Robert Haas wrote:
> On Tue, Oct 19, 2010 at 5:42 PM, Andrew Dunstan<andrew(at)dunslane(dot)net> wrote:
>> Well a bit more testing shows some benefit. I've sorted out a few kinks, so
>> this seems to work. In particular, with the above tables, the version
>> imported from 9.0 can create have an index created in about the same time as
>> on the fresh table (identical data, but all even numbered Oids).
>>
>> Of course, with lots of odd numbered Oids, if a label gets added the
>> imported version will degrade in performance much more quickly.
> I'm quite impressed by the amount of time and thought being put into
> optimizing this. I didn't realize people cared so much about enum
> performance; but it's good that they do.
>
> I hope to see more such efforts in other parts of the system.

:-)

Efficiency has always been one of the major reasons for using enums, so
it's important that we make them extensible without badly affecting
performance.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Terri Laurenzo 2010-10-20 01:15:52 Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP)
Previous Message Robert Haas 2010-10-20 00:53:07 Re: Serializable snapshot isolation patch