On Sun, 2004-07-11 at 20:57, Bruce Momjian wrote: > I can do that for 7.6. Is it worth it? Is it a TODO?
I'm not sure what Christopher mentioned is the correct fix. The information is displayed correctly in all places except where a pg_get_.* function is used (indexes, constraints, etc.). Those functions are tailored to what pg_dump requires (escaped identifier: """vers""ion""") rather than what psql requires (unescaped identifier: "vers"ion"). Right now psql shows a mix of both. > Christopher Kings-Lynne wrote: > > > As a result of the constraint output functions being shared between > > > pg_dump and psql, some of the output is mis-quoted in the display area > > > for columns including quotes. Notice it's correct in the table Column > > > list, but the constraint has the escaped versions. > > > > It's misquoted because psql DOES NOT share the fmtId function with > > pg_dump. It simply puts double quotes around it. If you can fix psql > > so that it is able to link to the fmtId function, then you can easily > > fix the problem ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
