Re: pgsql: Make the pg_stat_activity view call a SRF
От | Bruce Momjian |
---|---|
Тема | Re: pgsql: Make the pg_stat_activity view call a SRF |
Дата | |
Msg-id | 200808160349.m7G3nbr10695@momjian.us обсуждение исходный текст |
Ответ на | Re: pgsql: Make the pg_stat_activity view call a SRF (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: pgsql: Make the pg_stat_activity view call a SRF
|
Список | pgsql-committers |
Magnus Hagander wrote: > Bruce Momjian wrote: > > Magnus Hagander wrote: > >>> Sure, see pg_timezone_abbrevs(), pg_timezone_names(). > >>> > >>> (This only started to work recently, which is why we have so many > >>> record-returning functions that don't do it that way. It might be > >>> an idea to fix them all sooner or later.) > >> Wow, that was easy. Not sure where I got the impression it was hard > >> from - probably last looked at it before it was made easy, and didn't > >> re-check :-) > >> > >> Updated the pg_stat_get_activity() function to use this. > >> > >> And yes, I agree that it's probably a very good idea to go over our > >> other SRFs and fix them all. I can take a look at that eventually, but > >> for now I think we stick it on the TODO? > > > > Added to TODO: > > > > * Fix system views like pg_stat_all_tables to use set-returning > > functions, rather than views of per-column functions > > Thanks, and while I approve of that TODO, that's not actually the one I > was talking about in the email. The one I was talking about was "change > builtin set-returning functions to use OUT parameters so you can query > them without knowing the result format" or something like that. > > So, please keep the one you added, but add this one as well. Uh, I need more details on this. Can you give an example? -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
В списке pgsql-committers по дате отправления: