Re: Really unique session ID - PID + connection timestamp?
От | Christoph Berg |
---|---|
Тема | Re: Really unique session ID - PID + connection timestamp? |
Дата | |
Msg-id | 20160409124003.GA2719@msg.df7cb.de обсуждение исходный текст |
Ответ на | Re: Really unique session ID - PID + connection timestamp? (Stephen Frost <sfrost@snowman.net>) |
Ответы |
Re: Really unique session ID - PID + connection timestamp?
|
Список | pgsql-general |
Re: Stephen Frost 2016-04-09 <20160409115712.GT10850@tamriel.snowman.net> > > Btw, what you are describing is exactly what %c in log_line_prefix > > does. > > That's not currently exposed at an SQL level anywhere though, is it? > Perhaps we should add a way to get that. Another thought would be to > essentially expose 'log_line_prefix()' at the SQL level but I'm not sure > that generally makes sense. We could also have an explicit function to > get MyStartTime, similar to pg_backend_pid(). I don't see how log_line_prefix() would make sense, but pg_session_identifier() (= %c) would make sense to have, in the same way that we have pg_backend_pid(), so the current session could be located in the logs. (Not sure if pg_session_identifier shouldn't also be a pg_stat_activity column, but that might be overkill. Maybe SELECT pg_session_identifier(pid) from pg_stat_activity; ?) MyStartTime is probably too specific. Christoph
В списке pgsql-general по дате отправления: