pg_casts view (was Re: date_trun() with timezones? (was Re: TIME column ...)) - Mailing list pgsql-general

From Alvaro Herrera
Subject pg_casts view (was Re: date_trun() with timezones? (was Re: TIME column ...))
Date
Msg-id 20081103195330.GX4509@alvh.no-ip.org
Whole thread Raw
In response to Re: date_trun() with timezones? (was Re: TIME column manipulation/comparison hangups)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_casts view (was Re: date_trun() with timezones? (was Re: TIME column ...))  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pg_casts view (was Re: date_trun() with timezones? (was Re: TIME column ...))  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-general
Tom Lane escribió:

> However, the interval version of the function can capture the time case
> because there's an implicit cast from time to interval:
>
> regression=# select casttarget::regtype,castcontext,castfunc::regprocedure from pg_cast where castsource =
'time'::regtype;
>        casttarget       | castcontext |                castfunc
> ------------------------+-------------+----------------------------------------
>  interval               | i           | "interval"(time without time zone)
>  time with time zone    | i           | timetz(time without time zone)
>  time without time zone | i           | "time"(time without time zone,integer)
> (3 rows)

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)

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-general by date:

Previous
From: Jason Long
Date:
Subject: Re: Debugging infrequent pegged out CPU usage
Next
From: Tom Lane
Date:
Subject: Re: pg_casts view (was Re: date_trun() with timezones? (was Re: TIME column ...))