postgres command-line tools
Clone or download
depesz Add pid, and fix long-query wrapping
1. Added pidfile in activity report
2. Made the activity report wrap correctly on larger terminals

Wrapping doesn't reset itself after one changes terminal size *while in
activity report*, but when you ctrl-c it, and restart report it will catch
terminal size change.
Latest commit 1e0d4eb Oct 2, 2011
Type Name Latest commit message Commit time
Failed to load latest commit information.
c Initial version, straight from SVN Sep 6, 2011
docs Fix license Sep 6, 2011
k clear f4-f8 keybindings Sep 6, 2011
s Add pid, and fix long-query wrapping Oct 2, 2011



To make use of Curo, you need to have:
1. psql (version 8.3 or later)
2. bash
3. dialog


1. Copy curo directory to your home directory as .curo
2. If your psql is using readline, add to your ~/.inputrc this line:
$include ~/.curo/docs/readline.inputrc
3. If your psql is using libedit, copy ~/.curo/docs/libedit.editrc to your
4. If you're unsure which library your psql is using, you can use:
   - ldd $( which psql )
   - or just do both steps - #2 and #3
5. It's done. F1-F8 keys in psql now give you access to Curo functionality

Curo content:

In ~/.curo/ directory there are following elements:
1. docs directory - contains readline/libedit configuration files plus some
2. k directory - contains sql scripts which will be called when you press
   f1-f8 keys while in psql
3. s directory - this is where curo sql and shell scripts reside
4. c directory - common scripts used by action scripts from /s/

Scripts in k/ directory are overwritten by curo itself when you change
keybindings in setup screen, so changing them on your own is not good idea.
Instead you can add scripts in s/ and then set curo to call your script on
some f1-f8 keypress.


While we do test Curo on our own, you might encounter problems that we
didn't stumbled upon. In such case - contact for help.


Curo is distributed under The BSD 3-Clause license.