Re: Proposal: Store "timestamptz" of database creation on "pg_database" - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Proposal: Store "timestamptz" of database creation on "pg_database"
Date
Msg-id 20121229145949.GQ16126@tamriel.snowman.net
Whole thread Raw
In response to Re: Proposal: Store "timestamptz" of database creation on "pg_database"  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Responses Re: Proposal: Store "timestamptz" of database creation on "pg_database"  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
* Dimitri Fontaine (dimitri@2ndQuadrant.fr) wrote:
> It sounds to me like either autonomous transaction with the capability
> to run the independant transaction in another database, or some dblink
> creative use case. Another approach would be to get plproxy into core
> as a Foreign Data Wrapper for FOREIGN FUNCTION that would target
> PostgreSQL.
>
> Given that, we could maybe have an internal setup that allows us to run
> foreign functions in the postgres database from any other one, providing
> what we need for Global Event Triggers.

Of those, I'd think autonomous transactions is by far the most likely
and also useful for other sitatuions.  I don't see dblink or plproxy
being used for this.  Having some internal setup which allows us to run
foreign functions in other databases seems more-or-less akin to
autonomous transactions also.

> Oh, I don't see that happening in 9.3.

I agree, didn't mean to imply otherwise.
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Event Triggers: adding information
Next
From: Andres Freund
Date:
Subject: Re: Proposal: Store "timestamptz" of database creation on "pg_database"