Re: [HACKERS] TODO list

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] TODO list
Date: 2000-01-17 16:33:59
Message-ID: 38834477.B9037F62@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> The official SQL data types are "timestamp" and
> "interval", right? Everything else will eventually be an alias or
> phased out or whatever?

No (at least I haven't proposed that). abstime stays as a 4-byte
internal system time type. timestamp and interval become full-featured
date/time types, stealing all of the datetime and timespan code, and
the latter two become synonyms for timestamp and interval.

> I've been itching to change the pg_shadow.valuntil column to timestamp
> anyway, I suppose that would be a step in the right direction, or not?

At the moment, there are *no* 8-byte date/time types in the system
tables. This would be the first instance of that, and I'm not sure we
should introduce it in just one place.

Has abstime been a problem here?

- Thomas

--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2000-01-17 17:59:36 Re: [HACKERS] flex
Previous Message Bruce Momjian 2000-01-17 16:33:07 Re: [HACKERS] RE: Getting rid of setheapoverride (was Re: [COMMITTERS] heap.c)