Re: Proposal: Store "timestamptz" of database creation on "pg_database"
От | Stephen Frost |
---|---|
Тема | Re: Proposal: Store "timestamptz" of database creation on "pg_database" |
Дата | |
Msg-id | 20121229145949.GQ16126@tamriel.snowman.net обсуждение исходный текст |
Ответ на | Re: Proposal: Store "timestamptz" of database creation on "pg_database" (Dimitri Fontaine <dimitri@2ndQuadrant.fr>) |
Ответы |
Re: Proposal: Store "timestamptz" of database creation on
"pg_database"
|
Список | 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 по дате отправления: