On Tue, Dec 28, 2010 at 14:39, Robert Haas <robertmh...@gmail.com> wrote: > On Tue, Dec 28, 2010 at 7:49 AM, Magnus Hagander <mag...@hagander.net> wrote: >> Currently, a number of functions return data in a really >> calculation-unfriendly format, e.g: >> >> postgres=# select * from pg_current_xlog_location(); >> pg_current_xlog_location >> -------------------------- >> 0/3013158 >> (1 row) >> >> It would be very useful to have a way to convert this to a bigint - so >> we can do differences between different values easily. And it's AFAIUI >> easily converted to a 64-bit integer. >> >> Would others find this useful as well? > > Yes. > >> What's the best way of doing it? Should we have a function that takes >> text as input, or should the functions in question be made to return a >> new datatype that could then be casted? > > The new datatype seems more elegant, but a conversion function would > be a lot less work.
Well, yeah, that was obvious ;) The question is, how much do we prefer the more elegant method? ;) -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
