Tom Lane wrote:
Looking ahead to the future a bit, is there any reason to expect that
use_strict would have cross-function effects? In a normal Perl script
I suppose it does add some cross-function checking.
Not sure what you mean by this. Perl strict mode in fact does very
little chec
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
The one place that very slightly bothers me is the ::1 line in
pg_hba.conf. The fact that it comes last in the default config is its
saving grace - it won't ever be reached by a passing connection. I think
at least, though, we s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> The biggest problem is that "use" is in fact a forbidden operation in
> trusted plperl.
I would very much like to have use strict available in plperl. Is there
any way at all to simply make an exception for 'use strict' (and perhaps
some other pra
Greg Sabino Mullane said:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>> The biggest problem is that "use" is in fact a forbidden operation in
>> trusted plperl.
>
> I would very much like to have use strict available in plperl.
You're not alone. That's why we're going through all this
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> If you like, you can improve initdb to comment that line out if
>> getaddrinfo chokes on "::1", rather than believing HAVE_IPV6.
> Good idea. Here's a patch for that. Rather than commenting it out I used
> the slightly newer initdb f
