RFC: Adding \history [options] [filename] to psql (Snippets and Shared Queries) - Mailing list pgsql-hackers

From Kirk Wolak
Subject RFC: Adding \history [options] [filename] to psql (Snippets and Shared Queries)
Date
Msg-id CACLU5mRCnk4BjcT+R-vV-9A4GWU_+neine95QSf9mD47QP5QTA@mail.gmail.com
Whole thread Raw
Responses Re: RFC: Adding \history [options] [filename] to psql (Snippets and Shared Queries)
List 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 by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Let's make PostgreSQL multi-threaded
Next
From: Morris de Oryx
Date:
Subject: Re: [BUG] pg_dump does not properly deal with BEGIN ATOMIC function