[COMMITTERS] psqlodbc - psqlodbc: Remove a compilation error and some compiler

Log Message: --- Remove a compilation error and some compiler warnings under unixdODBC 2.3 environment. Modified Files: -- psqlodbc: misc.c (r1.55 -> r1.56) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/misc.c?r1=1.55&r2=1.56) misc.

[COMMITTERS] psqlodbc - psqlodbc: Make sure the support of the backward-compatibility

Log Message: --- Make sure the support of the backward-compatibility version of getaddrinfo() family even when _WIN32_WINNT is supplied. Modified Files: -- psqlodbc: socket.c (r1.71 -> r1.72) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/s

[COMMITTERS] pgsql: Use a separate interpreter for each calling SQL userid in plperl

Use a separate interpreter for each calling SQL userid in plperl and pltcl. There are numerous methods by which a Perl or Tcl function can subvert the behavior of another such function executed later; for example, by redefining standard functions or operators called by the target function. If the

[COMMITTERS] pgsql: Use a separate interpreter for each calling SQL userid in plperl

Use a separate interpreter for each calling SQL userid in plperl and pltcl. There are numerous methods by which a Perl or Tcl function can subvert the behavior of another such function executed later; for example, by redefining standard functions or operators called by the target function. If the

[COMMITTERS] pgsql: Use a separate interpreter for each calling SQL userid in plperl

Use a separate interpreter for each calling SQL userid in plperl and pltcl. There are numerous methods by which a Perl or Tcl function can subvert the behavior of another such function executed later; for example, by redefining standard functions or operators called by the target function. If the

[COMMITTERS] pgsql: Use a separate interpreter for each calling SQL userid in plperl

Use a separate interpreter for each calling SQL userid in plperl and pltcl. There are numerous methods by which a Perl or Tcl function can subvert the behavior of another such function executed later; for example, by redefining standard functions or operators called by the target function. If the

[COMMITTERS] pgsql: Use a separate interpreter for each calling SQL userid in plperl

Use a separate interpreter for each calling SQL userid in plperl and pltcl. There are numerous methods by which a Perl or Tcl function can subvert the behavior of another such function executed later; for example, by redefining standard functions or operators called by the target function. If the

[COMMITTERS] pgsql: Use a separate interpreter for each calling SQL userid in plperl

Use a separate interpreter for each calling SQL userid in plperl and pltcl. There are numerous methods by which a Perl or Tcl function can subvert the behavior of another such function executed later; for example, by redefining standard functions or operators called by the target function. If the

[COMMITTERS] pgsql: Use a separate interpreter for each calling SQL userid in plperl

Use a separate interpreter for each calling SQL userid in plperl and pltcl. There are numerous methods by which a Perl or Tcl function can subvert the behavior of another such function executed later; for example, by redefining standard functions or operators called by the target function. If the

[COMMITTERS] pgsql: Use a separate interpreter for each calling SQL userid in plperl

Use a separate interpreter for each calling SQL userid in plperl and pltcl. There are numerous methods by which a Perl or Tcl function can subvert the behavior of another such function executed later; for example, by redefining standard functions or operators called by the target function. If the

[COMMITTERS] psqlodbc - psqlodbc: Update win64.mak so that gssapi support is

Log Message: --- Update win64.mak so that gssapi support is available without libpq. Modified Files: -- psqlodbc: version.h (r1.166 -> r1.167) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/version.h?r1=1.166&r2=1.167) win64.mak (r1.

[COMMITTERS] pgsql: Undo some poorly-thought-out "proofreading improvements".

Undo some poorly-thought-out "proofreading improvements". Per Tatsuhito Kasahara. Branch -- master Details --- http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=d79a1a138e5dc9bc190b907e754268e819678a2a Modified Files -- doc/src/sgml/user-manag.sgml | 16 +

[COMMITTERS] pgsql: Undo some poorly-thought-out "proofreading improvements".

Undo some poorly-thought-out "proofreading improvements". Per Tatsuhito Kasahara. Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=6f1e6b9ccd6f7515063d466ef5ad1bd38b347be1 Modified Files -- doc/src/sgml/user-manag.sgml | 1

[COMMITTERS] pgsql: Correct docs for behaviour of ALTER DATABASE .. RENAME during Ho

Correct docs for behaviour of ALTER DATABASE .. RENAME during Hot Standby. Actual behaviour did not match documented behaviour and we have agreed that it should be the docs that change. Spotted by Bernd Helmle Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/gitweb?p=postgre

[COMMITTERS] pgsql: Correct docs for behaviour of ALTER DATABASE .. RENAME during Ho

Correct docs for behaviour of ALTER DATABASE .. RENAME during Hot Standby. Actual behaviour did not match documented behaviour and we have agreed that it should be the docs that change. Spotted by Bernd Helmle Branch -- master Details --- http://git.postgresql.org/gitweb?p=postgresql.git