Re: [BUGS] BUG #2931: Can't capture pg_dump Password prompt
On Sun, Jan 28, 2007 at 09:51:11AM -0700, Michael Schmidt wrote: > Mr. Hagander, > I have taken the discussion of the password issue to the General group. > Again, thanks. There are still two minor issues. > > 1. Entering pg_restore at the command prompt without any parameters hangs. > Shouldn't it exit neatly with an error message? No. It will then try to read the information from stdin. See http://www.postgresql.org/docs/8.2/static/app-pgrestore.html, under Optinos. > 2. The pg_dump application help (pg_dump --help) states both -U and > --username= are valid while the manual (section VI) only mentions -U. Should > the manual entry be edited? Yes, I beleive so. Same problems are present for at least -W also, and also present on pg_restore. so yes, that should be fixed. I'll try to put together a patch unless beaten to it. //Magnus ---(end of broadcast)--- TIP 6: explain analyze is your friend
[BUGS] BUG #2942: information_schema.element_types: documentation error
The following bug has been logged online: Bug reference: 2942 Logged by: Kirill Simonov Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2 Operating system: Linux Description:information_schema.element_types: documentation error Details: The page http://www.postgresql.org/docs/8.2/interactive/infoschema-element-types.html contains obsolete information. The example query SELECT c.column_name, c.data_type, e.data_type AS element_type FROM information_schema.columns c LEFT JOIN information_schema.element_types e ON ((c.table_catalog, c.table_schema, c.table_name, 'TABLE', c.dtd_identifier) = (e.object_catalog, e.object_schema, e.object_name, e.object_type, e.array_type_identifier)) WHERE c.table_schema = '...' AND c.table_name = '...' ORDER BY c.ordinal_position; fails with ERROR: column e.array_type_identifier does not exist. The fix is to replace 'e.array_type_identifier' with e'dtd_identifier'. The column array_type_identifier described in the Table 32-17 does not exists. The column dtd_identifier, which is described as "This is currently not useful.", should have he description of the former array_type_identifier column. ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [BUGS] BUG #2931: Can't capture pg_dump Password prompt
Mr. Hagander, I have taken the discussion of the password issue to the General group. Again, thanks. There are still two minor issues. 1. Entering pg_restore at the command prompt without any parameters hangs. Shouldn't it exit neatly with an error message? 2. The pg_dump application help (pg_dump --help) states both -U and --username= are valid while the manual (section VI) only mentions -U. Should the manual entry be edited? Thanks again for all your time. Michael Schmidt
