Re: timestamp resolution?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: thomas(at)pgsql(dot)com
Cc: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: timestamp resolution?
Date: 2001-10-04 14:46:23
Message-ID: 19725.1002206783@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Lockhart <lockhart(at)fourpalms(dot)org> writes:
> Even stranger, this only happens on the first call to CURRENT_TIMESTAMP
> after starting a backend (example below), and stays that way if I just
> do "select current_timestamp". Something must not be initialized quite
> right, but I don't know what. Any guesses?

Ah, I've got it. Two problems: AdjustTimestampForTypmod is one brick
shy of a load, and the hardwired calls to timestamp_in and friends
weren't passing all the parameters they should. (Can anyone think of
a way for DirectFunctionCall to do any checking?)

Patch will be committed in a moment...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-10-04 15:27:04 Beta time
Previous Message Zeugswetter Andreas SB SD 2001-10-04 14:41:34 Re: [HACKERS] Problem on AIX with current