Re: New functions in sslinfo module
От | Воронин Дмитрий |
---|---|
Тема | Re: New functions in sslinfo module |
Дата | |
Msg-id | 636781405663952@web15g.yandex.ru обсуждение исходный текст |
Ответ на | Re: New functions in sslinfo module (Andreas Karlsson <andreas@proxel.se>) |
Ответы |
Re: New functions in sslinfo module
|
Список | pgsql-hackers |
<p>Hello, Andreas and others!<br /><br />I make a new version of patch. I corrected your notes for my <span lang="en"><span>previousversion of patch. Could you test it? Thank you.</span></span><br /><br />03.07.2014, 01:54, "AndreasKarlsson" <<a href="mailto:andreas@proxel.se">andreas@proxel.se</a>>:<blockquote> On 07/02/2014 02:17 PM, ВоронинДмитрий wrote:<br /><blockquote> I apologize, that I am writing this message today. Thank you for testing<br /> mypatch!</blockquote> You are welcome!<br /><blockquote> I will modify functions ssl_extensions(), that it returns aset (key,<br /> value). Could you get me an example of code those function?</blockquote> You can look at hstore_each()in hstore_op.c.<br /><blockquote><blockquote><blockquote><blockquote> - Why are X509_NAME_field_to_text(),X509_NAME_to_text(),</blockquote></blockquote></blockquote> ASN1_STRING_to_text() and get_extension()not static? None of these are<br /> a symbol which should be exported.<br /><blockquote><blockquote><blockquote> Whydo you use pg_do_encoding_conversion() over pg_any_to_server()?</blockquote></blockquote></blockquote> pg_any_to_server()is implemented using pg_do_encoding_conversion().<br/><br /> I don't write a code of those functions and I can't answer on your question.</blockquote> Hm,I thought I saw them changed from static to not in the diff after<br /> applying your patch. MaybeI just misread the patch.<br /><br /> --<br /> Andreas Karlsson</blockquote><p>-- <br />Best regards, Dmitry Voronin
В списке pgsql-hackers по дате отправления: