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

Re: Event Triggers reduced, v1

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 15:52:00
Message-ID: m2a9zgj10f.fsf@2ndQuadrant.fr (view raw or flat)
Thread:
Lists: pgsql-hackers
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> in it.  That's more or less what Dimitri already has in his latest
> patch, except that after looking it over I'm inclined to think that
> we'd be better off storing the keys as text and translating to
> internal ID numbers when we read and cache the table, rather than
> storing the ID numbers in the table.  That will make the catalog
> contents easier to read, and more importantly will mean that a change
> to the internal ID numbers need not be initdb-forcing.

Well that's what I had in previous versions of the patch, where the code
was dealing directly with command tags. If we store text in catalogs and
given that we already have the command tag as text, I suppose we would
get back to only managing tags as text in the cache key and the rest of
the code.

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support

In response to

Responses

pgsql-hackers by date

Next:From: Andres FreundDate: 2012-07-03 15:55:30
Subject: Re: Posix Shared Mem patch
Previous:From: Tom LaneDate: 2012-07-03 15:51:29
Subject: Re: Ability to listen on two unix sockets

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