From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Function for dealing with xlog data |
Date: | 2010-12-28 12:49:06 |
Message-ID: | AANLkTinE2+CMxTscP1SP3RSL7Z=v2gR42F_CcSYVZr2G@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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?
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?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Itagaki Takahiro | 2010-12-28 13:14:19 | Re: system views for walsender activity |
Previous Message | Magnus Hagander | 2010-12-28 12:46:33 | Re: system views for walsender activity |