Re: Consistent \d commands in psql
От | Bruce Momjian |
---|---|
Тема | Re: Consistent \d commands in psql |
Дата | |
Msg-id | 200711051744.lA5Hi2M14861@momjian.us обсуждение исходный текст |
Ответ на | Consistent \d commands in psql (Greg Sabino Mullane <greg@turnstep.com>) |
Список | pgsql-patches |
This has been saved for the 8.4 release: http://momjian.postgresql.org/cgi-bin/pgpatches_hold --------------------------------------------------------------------------- Greg Sabino Mullane wrote: > Attached is an updated version of my psql patch that makes the \d > backslash commands perform in an intuitive, consistent way. > Specifically, the following objects will be treated as first class > citizens (as tables and indexes currently are) by showing all the > non-system objects by default and requiring a "S" to see the system > ones. > > aggregates > conversions > comments > domains > operators > functions > types > > Currently, there is no way to view all the non-system functions in a > database using backslash commands, as you can with \dt, unless all of > the functions happen to be in a single schema ("\df myschema."). With > this patch, it would be as simple as "\df", and the current behavior > would be done with "\dfS". > > This patch also adds a few new things to the tab-completion table, such > as comments and conversions. > > Comments welcome. Last time the patch withered on the vine, despite > strong support from -general, hence I'm going to try again, as I really > want a way to view my functions without querying the pg_proc tables > directly. :) > > -- > Greg Sabino Mullane greg@turnstep.com > PGP Key: 0x14964AC8 200711042003 > http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 > [ Attachment, skipping... ] > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
В списке pgsql-patches по дате отправления: