[BUGS] BUG #1418: RFC: Challenge/response authentication support
The following bug has been logged online: Bug reference: 1418 Logged by: Craig Ruff Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0 Operating system: Any Description:RFC: Challenge/response authentication support Details: PAM supports challenge response authentication. It is desirable that psql and the backend support this by displaying the PAM conversation routine message(s) and returing a response (optionally echoed to the user). I had a look at the code, and the backend support isn't too bad, but psql itself does not appear to be structured in a way to handle this easily. The current method of just closing the backend connection, prompting for the password and trying again does not work since the one-time password challenge/response method is stateful. Unfortunately, at the moment, I don't have the time to delve into fixing this up further, but thought I'd let the list know in case someone else is hacking on psql. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[BUGS] 8.0.0 pg_restore -L doesn't restore ACLs
PostgreSQL 8.0.0 Running "pg_restore -l" to create a list file and then restoring using "pg_restore -L" fails to restore ACLs. See the "Privileges where [sic] not restored" thread in pgsql-admin: http://archives.postgresql.org/pgsql-admin/2005-01/msg00197.php As I mention in a followup in that thread, the following restores objects with their ACLs: pg_restore -d testdb db.dump The following doesn't restore ACLs: pg_restore -l db.dump > db.list pg_restore -d testdb -L db.list db.dump -- Michael Fuhr http://www.fuhr.org/~mfuhr/ ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[BUGS] 8.0 doesn't dump index tablespace correctly.
Hi, pg_dump on 8.0 can't dump index's tablespace information if both table and its index 's tablespaces are different. For example: create table a(i int) tablespace ts1; create index a_idx on a (i) tablespace ts2; create index a_idx2 on a (i) tablespace pg_default; Assuming tablespace ts1 ans ts2 were defined. If dump and restore them , tablespace of a_idx and a_idx2 was ts1 , which is a's tablespace ,not index's one . Here's a patch . *** pg_dump.c.orig 2005-01-20 15:14:28.0 +0900 --- pg_dump.c 2005-01-20 15:14:53.0 +0900 *** *** 6899,6905 ArchiveEntry(fout, indxinfo->dobj.catId, indxinfo->dobj.dumpId, indxinfo->dobj.name, tbinfo->dobj.namespace->dobj.name, !tbinfo->reltablespace, tbinfo->usename, false, "INDEX", q->data, delq->data, NULL, indxinfo->dobj.dependencies, indxinfo->dobj.nDeps, --- 6899,6905 ArchiveEntry(fout, indxinfo->dobj.catId, indxinfo->dobj.dumpId, indxinfo->dobj.name, tbinfo->dobj.namespace->dobj.name, !indxinfo->tablespace, tbinfo->usename, false, "INDEX", q->data, delq->data, NULL, indxinfo->dobj.dependencies, indxinfo->dobj.nDeps, -- TANIDA Yutaka <[EMAIL PROTECTED]> ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
