Skip site navigation (1) Skip section navigation (2)

Re: Event Triggers reduced, v1

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Event Triggers reduced, v1
Date: 2012-07-03 16:25:57
Message-ID: CA+TgmoZzRxcTBgT3BfYb046KQCaVodCN9DjoiwKDZcoNQ2aN_g@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, Jul 3, 2012 at 12:18 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> Yeah, I'm of two minds on that.  I thought that it made sense to use
>> integer identifiers internally for speed, but now I'm worried that the
>> effort to translate back and forth between strings and integers is
>> going to end up being more than any speed we might save.
>
> We do that for nodetags in stored query/expression trees, and I've never
> seen any indication that it costs enough to notice.  It's definitely a
> huge win for anything that changes regularly, which seems like it'll be
> a pretty good description of event tags for at least the next few years.

Good analogy.  In that case, as in what I'm proposing here, we use
integers in memory and text on disk.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-hackers by date

Next:From: Pavel StehuleDate: 2012-07-03 16:26:57
Subject: Re: enhanced error fields
Previous:From: Tom LaneDate: 2012-07-03 16:18:47
Subject: Re: Event Triggers reduced, v1

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group