Re: Problems with avg on interval data type

Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
>> I suggest that the current code is more correct than you think ;-).
>> ISTM it is a good idea to require a units field, or at least some
>> punctuation giving a clue about units --- for example I do not object to
>> '08:00' being interpreted as hours and minutes.  But I would be inclined
>> to reject all four of the forms '+8', '-8', '8.0', and '8' as ambiguous.
>> Is there something in the SQL spec that requires us to accept them?

> Single-field signed integers (and unsigned integers?) must be acceptable
> for a time zone specification (pretty sure this is covered in the SQL
> spec).

But surely there is other context cuing you that the number is a
timezone?  In any case, you weren't proposing that interval_in
should accept '8' as a timezone ...

			regards, tom lane