| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, fabriziomello(at)gmail(dot)com, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" |
| Date: | 2013-01-03 01:35:00 |
| Message-ID: | CA+TgmoYwgCyK55PoHzW-hk+gs=C9AyAUYmHs4GXUzRT1zbJnnQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Dec 29, 2012 at 10:26 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> A shared table for event triggers sounds like it would be the far easier
> solution (9.4+ that is).
The problem is that the event trigger table is a just a pointer to a
function, and there's no procedure OID to store in that shared catalog
unless you also have a proposal for making pg_proc into a shared
catalog ... which would also require making pg_language into a shared
catalog, and maybe a few others.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-01-03 01:52:27 | Re: Proposal: Store "timestamptz" of database creation on "pg_database" |
| Previous Message | Tom Lane | 2013-01-02 23:40:13 | Re: dynamic SQL - possible performance regression in 9.2 |