<div dir="ltr">On Wed, May 20, 2015 at 2:40 AM, Jim Nasby <<a
href="mailto:Jim.Nasby@bluetreble.com">Jim.Nasby@bluetreble.com</a>>wrote:<br />><br />> On 5/19/15 9:19 PM,
Fabríziode Royes Mello wrote:<br />>><br />>> We could add a second parameter to the current
functions:<br/>>> allow_own_pid DEFAULT false. To me that seems better than an<br />>> entirely
separateset of functions.<br />>><br />>><br />>> +1 to add a second parameter to current
functions.<br/>><br />><br />> Instead of allow_own_pid, I went with skip_own_pid. I have the function still
returningtrue even when it skips it's own PID... that seems a bit weird, but I think it's better than returning false.
Unlesssomeone thinks it should return NULL, but I don't see that as any better either.<br />><br /><br />Isn't
betteruse 'false' as the default value of the new parameter?<br /><br />Regards,<br /><br />--<br />Fabrízio de Royes
Mello<br/>Consultoria/Coaching PostgreSQL<br />>> Timbira: <a
href="http://www.timbira.com.br">http://www.timbira.com.br</a><br/>>> Blog: <a
href="http://fabriziomello.github.io">http://fabriziomello.github.io</a><br/>>> Linkedin: <a
href="http://br.linkedin.com/in/fabriziomello">http://br.linkedin.com/in/fabriziomello</a><br/>>> Twitter: <a
href="http://twitter.com/fabriziomello">http://twitter.com/fabriziomello</a><br/>>> Github: <a
href="http://github.com/fabriziomello">http://github.com/fabriziomello</a></div>