Re: [PATCH] Fix NULL checking in check_TSCurrentConfig()

From: "Dickson S(dot) Guedes" <listas(at)guedesoft(dot)net>
To: Xi Wang <xi(dot)wang(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] Fix NULL checking in check_TSCurrentConfig()
Date: 2013-01-20 14:48:16
Message-ID: CAHHcrermpVwAFcheRkPyVO6pNb6cmHzHE4YzCA3eq5-Zdzh7HA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2013/1/20 Xi Wang <xi(dot)wang(at)gmail(dot)com>:
> The correct NULL check should use `*newval'; `newval' must be non-null.

[... cutting code ...]

Please see [1] to know how is our submit patch process.

[1] http://wiki.postgresql.org/wiki/Submitting_a_Patch

regards,
--
Dickson S. Guedes
mail/xmpp: guedes(at)guedesoft(dot)net - skype: guediz
http://github.com/guedes - http://guedesoft.net
http://www.postgresql.org.br

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2013-01-20 14:52:09 Re: Query to help in debugging
Previous Message Robert Haas 2013-01-20 14:10:47 Re: allowing privileges on untrusted languages