Arnau <arnaulist(at)andromeiberica(dot)com> writes:
>> Alternatively, do you really need to_timestamp at all? The standard
>> timestamp input routine won't have any problem with that format:
>> t.timestamp_in >= '20070101'
> This is always I think I'm worried, what happens if one day the internal
> format in which the DB stores the date/timestamps changes. I mean, if
> instead of being stored as YYYYMMDD is stored as DDMMYYYY, should we
> have to change all the queries?
You are confusing internal storage format with the external
> I thought the
> to_char/to_date/to_timestamp functions were intented for this purposes
No, they're intended for dealing with wacky formats that the regular
input/output routines can't understand or produce.
regards, tom lane
In response to
pgsql-performance by date
|Next:||From: Karl Denninger||Date: 2007-07-25 01:20:09|
|Subject: Performance issue with 8.2.3 - "C" application|
|Previous:||From: Arnau||Date: 2007-07-24 19:31:07|
|Subject: Re: index over timestamp not being used|