From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
---|---|
To: | "Guillaume Bog" <guibog(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: finding a column by name in psql |
Date: | 2007-03-12 16:01:41 |
Message-ID: | b42b73150703120901k53bdeb17vd195e783af16e524@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 3/12/07, Guillaume Bog <guibog(at)gmail(dot)com> wrote:
> Hi everyone,
>
> I'm now used to using psql to manage my databases into a terminal, and
> I found the very convenient "\g |" command that pipes query result in
> any shell tool I want. But I still have hard time finding some columns
> in some tables (that may have 300+ cols). I would like to pipe the
> result of "\d" mytable in some grep but it doesn't work. I have done
> it once or twice by SELECTing pg_attrib but this requires a lot of
> typing. I tried to store a procedure but apparently I don't have any
> language allowed... I'm sure it could do it but and I wondering if I
> missed some simpler command that would allow me to conveniently search
> into database structure. i.e. something like "\d mytable *_ts" that
> could display all cols in mytable ending with "_ts".
Have you tried configuring your pager? I use:
env:
PAGER=less
LESS='-iMSx4 -FX'
psql:
/pset pager=always
this allows for spreadsheet style navigation of psql results and you
can use search feature of less (slash) to highlight columns/data.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Jones | 2007-03-12 16:14:14 | Tracking disk writes? (again) |
Previous Message | Guillaume Bog | 2007-03-12 15:29:26 | finding a column by name in psql |