On Thu, Oct 21, 2010 at 10:24 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Bruce Momjian <br...@momjian.us> writes: >> Greg Stark wrote: >>> Did we have a solution for the problem that understanding which >>> columns are timestamps requires having a tuple descriptor and parsing >>> the every tuple? That seems like it would a) be slow and b) require a >>> lot of high level code in the middle of a low-level codepath. > >> Yep, that's what it requires. It would rewrite in the new format. > > In the case of the recent hstore fixes, we were able to put the burden > on the hstore functions themselves to do any necessary conversion. > I wonder if it'd be possible to do something similar here? I haven't > chased the bits in any detail, but I'm thinking that integer timestamps > in a plausible range might all look like denormalized floats, and > conversely plausible float timestamps would look like ridiculously large > integer timestamps. Would we be willing to make such assumptions to > support in-place upgrade of timestamps?
This seems like it might not be entirely reliable, which would make me disinclined to do it. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
