Re: let's make the list of reportable GUCs configurable (was Re: Add %r substitution for psql prompts to show recovery status)
От | Tom Lane |
---|---|
Тема | Re: let's make the list of reportable GUCs configurable (was Re: Add %r substitution for psql prompts to show recovery status) |
Дата | |
Msg-id | 21454.1515617707@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: let's make the list of reportable GUCs configurable (was Re: Add%r substitution for psql prompts to show recovery status) (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: let's make the list of reportable GUCs configurable (was Re: Add%r substitution for psql prompts to show recovery status)
Re: let's make the list of reportable GUCs configurable (was Re: Add%r substitution for psql prompts to show recovery status) |
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > But if we add this feature and somebody wants to use it for > server_version_num, it's really pretty simple. In the startup packet, > you say _pq_.report=server_version_num. Then, you call > PQparameterStatus(conn, "server_version_num"). If you don't get a > value, you try calling PQparameterStatus(conn, "server_version") and > extracting the second word. If that still doesn't work then you give > up. That doesn't seem either useless or difficult to implement > correctly from here. Yeah, but what's the point? If yuou have to maintain the server_version parsing code anyway, you're not saving any complexity with this. You're just creating a code backwater that you probably won't test adequately. regards, tom lane
В списке pgsql-hackers по дате отправления: