Re: Timestamp docs weirdness

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Marcus Brger <mail(at)marcus-boerger(dot)de>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Timestamp docs weirdness
Date: 2003-10-27 18:10:45
Message-ID: 815.1067278245@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> OK, do we want to put back the mention of these in the release notes?
> The non-zulu ones sound pretty strange to me and might be better left
> undocumented.

AFAICS the updated docs are correct. Since the code behavior has not
changed, there is no need for a release-notes entry, is there?

>> Only the combination of both doesn't work:
>> template1=# select 'allballs zulu'::timetz;
>> ERROR: Bad time external representation 'allballs zulu'

That's because 'allballs' is defined as '00:00:00 UTC', that is,
it already defines a timezone. The above is a double specification
of timezone and gets the same error as

regression=# select '00:00:00 UTC UTC'::timetz;
ERROR: invalid input syntax for type time with time zone: "00:00:00 UTC UTC"

I see no bug here.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message strk 2003-10-27 18:57:04 Re: DETOASTing in custom memory context
Previous Message Thiago Fernandes Moesch 2003-10-27 17:52:16 When the last vacuum occured? It's necessary to run it now?

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2003-10-27 18:14:44 Re: ISM shared memory on solaris
Previous Message Tom Lane 2003-10-27 17:14:05 Re: PostgreSQL Patch: Test-and-set routine for HP-UX (IA-64)