Re: [HACKERS] Rounding issue with current_time

2001-10-03 Thread Thomas Lockhart
> BTW, would you object to my removing the macros > IS_BUILTIN_TYPE(), IS_HIGHER_TYPE(), IS_HIGHEST_TYPE() > from parse_coerce.h? They are used nowhere and are not > being maintained --- eg, they don't seem to know about > TIMESTAMPTZ. OK. I had already stripped out some "#if NOT_USED" code but

Re: [HACKERS] Rounding issue with current_time

2001-10-03 Thread Thomas Lockhart
... > So the real issue appears to be that subsecond resolution isn't > propagating into time and timetz at all. Ah. Of course it isn't, because I (probably) didn't change DecodeTimeOnly() to use the microsecond resolution version of the transaction time. Will look at it.

Re: [HACKERS] Rounding issue with current_time

2001-10-03 Thread Tom Lane
BTW, would you object to my removing the macros IS_BUILTIN_TYPE(), IS_HIGHER_TYPE(), IS_HIGHEST_TYPE() from parse_coerce.h? They are used nowhere and are not being maintained --- eg, they don't seem to know about TIMESTAMPTZ. regards, tom lane ---

Re: [HACKERS] Rounding issue with current_time

2001-10-03 Thread Thomas Lockhart
... > It's fairly disconcerting that f2 and f3 don't agree, wouldn't you say? :) I'll look at it. - Thomas ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] Rounding issue with current_time

2001-10-03 Thread Tom Lane
Further experimentation: regression=# create table foo3 (f1 date default current_date, regression(# f2 time(3) default current_time, regression(# f3 timestamp(3) default current_timestamp); CREATE regression=# insert into foo3 default values; (multiple times) regression=# select * from foo3;

[HACKERS] Rounding issue with current_time

2001-10-03 Thread Tom Lane
With current CVS, I did regression=# create table foo (f1 date default current_date, regression(# f2 time default current_time, regression(# f3 timestamp default current_timestamp); CREATE regression=# \d foo Table "foo" Column | Type |