Added to TODO: * Add a function like pg_get_indexdef() that report more detailed index information
http://archives.postgresql.org/pgsql-bugs/2007-12/msg00166.php --------------------------------------------------------------------------- Dave Page wrote: > Tom Lane wrote: > >> We use the data in various UI elements as well as for reverse > >> engineering the SQL - it's easier to get it broken down than to parse it > >> back out of the complete definition. > > > > Seems like all the more argument for having functions that extract > > single pieces of information, rather than several pieces (especially > > if some pieces get left off when default). > > Well it might well have been if the pgAdmin code didn't already work and > it wasn't so close to release :-) > > > For the moment I've reverted pg_get_indexdef() to its prior behavior > > of printing only the index column key or expression when colno!=0. > > We can look at having another function to do the other thing in 8.4. > > Thanks. > > /D > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
