Re: pg_casts view (was Re: date_trun() with timezones? (was Re: TIME column ...))

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Bill Moran <wmoran(at)collaborativefusion(dot)com>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: pg_casts view (was Re: date_trun() with timezones? (was Re: TIME column ...))
Date: 2008-11-05 12:18:17
Message-ID: 49118F09.7080808@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
>> Tom Lane escribi�:
>>> regression=# select casttarget::regtype,castcontext,castfunc::regprocedure from pg_cast where castsource = 'time'::regtype;
>
>> BTW it very much looks like we should have a pg_casts view that displays
>> these things in a human-readable manner (like the above except with
>> castcontext expanded)
>
> There already is a \dC command in psql, which has nice enough output
> format but doesn't provide any way to select a subset of the table.
> Maybe we should just agree that its argument is a pattern for the
> castsource type's name?

I'd say it could be a pattern for both source and target. Often times I
am interested in casts in either direction.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mohammad Ali Darvish Darab 2008-11-05 12:18:37 Visualizer
Previous Message Peter Eisentraut 2008-11-05 12:17:01 Re: pg_casts view (was Re: date_trun() with timezones? (was Re: TIME column ...))