RFC: Adding \history [options] [filename] to psql (Snippets and Shared Queries)

Поиск
Список
Период
Сортировка
От Kirk Wolak
Тема RFC: Adding \history [options] [filename] to psql (Snippets and Shared Queries)
Дата
Msg-id CACLU5mRCnk4BjcT+R-vV-9A4GWU_+neine95QSf9mD47QP5QTA@mail.gmail.com
обсуждение исходный текст
Ответы Re: RFC: Adding \history [options] [filename] to psql (Snippets and Shared Queries)  (Gurjeet Singh <gurjeet@singh.im>)
Список pgsql-hackers
Everyone,
  After recently deep diving on some readline features and optimizing my bash environment to have a static set of "snippets" that I can always find...

  it takes just a couple of history API calls to add some interesting features for those  that want them.  The result of adding 3-4 such commands (all under \history, and with compatible flags):

- Saving your current history without exiting (currently doable as \s :HISTFILE)
- Reloading your history file (so you can easily share something across sessions) w/o exiting.
- Stack Loading of specific history (like a shared snippets library, and a personal snippets library) [clearing your history, then loading them in a custom order]

  The upside is really about clearly identifying and sharing permanent snippets, while having that list be editable externally.  Again, bringing teams online who don't always know the PG way of doing things (Waits, Locks, Space, High CPU queries, Running Queries).

  My intention is to leverage the way PSQL keeps the Comment above the SQL with the SQL.
Then I can step backwards searching for "context" markers (Ctrl-R) or
-- <CONTEXT> [F8] {history-search-backward}

  To rip through my snippets

Kirk...
PS: I could do all of this under \s [options] [filename] it's just less clear...

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Heikki Linnakangas
Дата:
Сообщение: Re: Let's make PostgreSQL multi-threaded
Следующее
От: Morris de Oryx
Дата:
Сообщение: Re: [BUG] pg_dump does not properly deal with BEGIN ATOMIC function