Re: New functions in sslinfo module

<div>I put patch generated on git diffs to this letter. I make an a thread in postgresql commit fest:
https://commitfest.postgresql.org/action/patch_view?id=1438</div><div> </div><div>21.04.2014,09:12, "Michael Paquier"
<michael.paquier@gmail.com>:</div><blockquotetype="cite"><div><div><br /><br />On Mon, Apr 21, 2014 at 1:48 PM,
ВоронинДмитрий <<a href="mailto:carriingfate92@yandex.ru">carriingfate92@yandex.ru</a>> wrote:<br />>
Hello,<br/>>  <br />> I make an a patch, which adds 4 functions to sslinfo extension module:<br /> > 1)
ssl_get_count_of_extensions()--- get count of X509v3 extensions from<br />> client certificate;<br />> 2)
ssl_get_extension_names()--- get short names of X509v3 extensions from<br />> client certificate;<br />> 3)
ssl_get_extension_value(text)--- get value of extension from certificate<br /> > (argument --- short name of
extension);<br/>> 4) ssl_is_critical_extension(text) --- returns true, if extension is<br />> critical and false,
ifis not (argument --- short name of extension).<br />>  <br />> You can view some information of certificate's
extensionsvia those<br /> > functions.<br />> I want, that my functions will be included in PostgreSQL
release.<br/>>  <br />> What do you think about it?<br />Please avoid creating a new thread each time you send a
newversion of the same patch. Previous message was here:<br /><a
href="http://www.postgresql.org/message-id/1135491397673046@web9m.yandex.ru">http://www.postgresql.org/message-id/1135491397673046@web9m.yandex.ru</a><br
/>Withmy previous answer here:<br /><a
href="http://www.postgresql.org/message-id/CAB7nPqRVFhnPnQL9ND+K=WA-YF_N1fAirx=s6fawk9F6ANLwBQ@mail.gmail.com">http://www.postgresql.org/message-id/CAB7nPqRVFhnPnQL9ND+K=WA-YF_N1fAirx=s6fawk9F6ANLwBQ@mail.gmail.com</a><span></span><span></span><br
/><br/>As I already mentioned last time, please register this patch to the upcoming commit fest beginning in June:<br
/><ahref="https://commitfest.postgresql.org/action/commitfest_view?id=22"
target="_blank">https://commitfest.postgresql.org/action/commitfest_view?id=22</a></div><div>Thisway, you will be sure
thatyour patch will get at least one fair review and that progress will be made on the feature you are
proposing.</div><div><br/>The development cycle of 9.4 is over, but your patch could get into 9.5. You seem as well to
havedeveloped this patch using a tarball of 9.3.4 code by generating diffs from it, you will need a development
environmentwith git. Here are some guidelines you can refer to (those are the same URLs as in my previous email
btw...):<br/><a href="https://wiki.postgresql.org/wiki/Submitting_a_Patch"
target="_blank">https://wiki.postgresql.org/wiki/Submitting_a_Patch</a><br/><a
href="https://wiki.postgresql.org/wiki/Working_with_Git"
target="_blank">https://wiki.postgresql.org/wiki/Working_with_Git</a><br/><a
href="https://wiki.postgresql.org/wiki/Creating_Clean_Patches"
target="_blank">https://wiki.postgresql.org/wiki/Creating_Clean_Patches</a></div>Regards,<br/><div><div>-- <br
/>Michael</div></div></div></blockquote><div> </div><div>Bestregrads, Dmitry Voronin</div><blockquote
type="cite"><div> </div></blockquote><div> </div>