[COMMITTERS] pgsql: Restrict non-superusers to password authenticated connections to

2007-07-08 Thread Joe Conway
Log Message: --- Restrict non-superusers to password authenticated connections to prevent possible escalation of privilege. Provide new SECURITY DEFINER functions with old behavior, but initially REVOKE ALL from public for these functions. Per list discussion and design proposed by Tom Lane

[COMMITTERS] pgsql: Restrict non-superusers to password authenticated connections to

2007-07-08 Thread Joe Conway
Log Message: --- Restrict non-superusers to password authenticated connections to prevent possible escalation of privilege. Provide new SECURITY DEFINER functions with old behavior, but initially REVOKE ALL from public for these functions. Per list discussion and design proposed by Tom Lane

[COMMITTERS] pgsql: Restrict non-superusers to password authenticated connections to

2007-07-08 Thread Joe Conway
Log Message: --- Restrict non-superusers to password authenticated connections to prevent possible escalation of privilege. Provide new SECURITY DEFINER functions with old behavior, but initially REVOKE ALL from public for these functions. Per list discussion and design proposed by Tom Lane

[COMMITTERS] pgsql: Restrict non-superusers to password authenticated connections to

2007-07-08 Thread Joe Conway
Log Message: --- Restrict non-superusers to password authenticated connections to prevent possible escalation of privilege. Provide new SECURITY DEFINER functions with old behavior, but initially REVOKE ALL from public for these functions. Per list discussion and design proposed by Tom Lane

[COMMITTERS] pgsql: Restrict non-superusers to password authenticated connections to

2007-07-08 Thread Joe Conway
Log Message: --- Restrict non-superusers to password authenticated connections to prevent possible escalation of privilege. Provide new SECURITY DEFINER functions with old behavior, but initially REVOKE ALL from public for these functions. Per list discussion and design proposed by Tom Lane

[COMMITTERS] pgsql: Fix single-user mode so that interrupts (particularly SIGTERM and

2007-07-08 Thread Tom Lane
Log Message: --- Fix single-user mode so that interrupts (particularly SIGTERM and SIGQUIT) will be recognized and processed while waiting for input, rather than only after something has been typed. Also make SIGQUIT do the same thing as SIGTERM in single-user mode, ie, do a normal shutdow

[COMMITTERS] pgsql: Minor copy-editing.

2007-07-08 Thread Tom Lane
Log Message: --- Minor copy-editing. Modified Files: -- pgsql/doc/src/sgml/ref: postgres-ref.sgml (r1.50 -> r1.51) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/postgres-ref.sgml.diff?r1=1.50&r2=1.51) ---(end of

[COMMITTERS] pgsql: Remove the pgstat_drop_relation() call from

2007-07-08 Thread Tom Lane
Log Message: --- Remove the pgstat_drop_relation() call from smgr_internal_unlink(), because we don't know at that point which relation OID to tell pgstat to forget. The code was passing the relfilenode, which is incorrect, and could possibly cause some other relation's stats to be zeroed o

[COMMITTERS] pgsql: Remove the pgstat_drop_relation() call from

2007-07-08 Thread Tom Lane
Log Message: --- Remove the pgstat_drop_relation() call from smgr_internal_unlink(), because we don't know at that point which relation OID to tell pgstat to forget. The code was passing the relfilenode, which is incorrect, and could possibly cause some other relation's stats to be zeroed o

[COMMITTERS] pgsql: Remove the pgstat_drop_relation() call from

2007-07-08 Thread Tom Lane
Log Message: --- Remove the pgstat_drop_relation() call from smgr_internal_unlink(), because we don't know at that point which relation OID to tell pgstat to forget. The code was passing the relfilenode, which is incorrect, and could possibly cause some other relation's stats to be zeroed o

[COMMITTERS] pgsql: Get rid of client-code dependencies on the exact text of the

2007-07-08 Thread Tom Lane
Log Message: --- Get rid of client-code dependencies on the exact text of the no-password error message, by using PQconnectionUsedPassword() instead. Someday we might be able to localize that error message, but not until this coding technique has disappeared everywhere. Modified Files: --

[COMMITTERS] pgsql: Closer code review for PQconnectionUsedPassword() patch: in

2007-07-08 Thread Tom Lane
Log Message: --- Closer code review for PQconnectionUsedPassword() patch: in particular, not OK to include postgres_fe.h into libpq-fe.h, hence declare it as returning int not bool. Modified Files: -- pgsql/doc/src/sgml: libpq.sgml (r1.236 -> r1.237) (http:

[COMMITTERS] pgsql: Fix broken markup.

2007-07-08 Thread Tom Lane
Log Message: --- Fix broken markup. Modified Files: -- pgsql/doc/src/sgml/ref: alter_view.sgml (r1.1 -> r1.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/alter_view.sgml.diff?r1=1.1&r2=1.2) ---(end of broadcas

[COMMITTERS] pgsql: Restrict non-superusers to password authenticated connections to

2007-07-08 Thread Joe Conway
Log Message: --- Restrict non-superusers to password authenticated connections to prevent possible escalation of privilege. Provide new SECURITY DEFINER functions with old behavior, but initially REVOKE ALL from public for these functions. Per list discussion and design proposed by Tom Lane

[COMMITTERS] pgsql: Arrange for the authentication request type to be preserved in

2007-07-08 Thread Joe Conway
Log Message: --- Arrange for the authentication request type to be preserved in PGconn. Invent a new libpq connection-status function, PQconnectionUsedPassword() that returns true if the server demanded a password during authentication, false otherwise. This may be useful to clients in gene