From: Mario Weilguni <mweilguni@sime.com>
To: pgsql-performance@postgresql.org
Subject: Re: index over timestamp not being used
Date: Wed, 25 Jul 2007 15:05:10 +0200
Message-ID: <200707251505.11182.mweilguni@sime.com> (raw)
In-Reply-To: <15140.1185306195@sss.pgh.pa.us>
References: <46A64475.3040201@andromeiberica.com>
<46A6537B.6010604@andromeiberica.com>
<15140.1185306195@sss.pgh.pa.us>
Am Dienstag 24 Juli 2007 schrieb Tom Lane:
> > 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.
Really? I use them alot, because of possible problems with different date
formats. 20070503 means May 3, 2007 for germans, I don't know what it means
to US citizens, but following the strange logic of having the month first
(8/13/2005) it might mean March 5, 2007 too. Therefore, using to_timestamp
seems to be a safe choice for me, working in any environment regardless of
the "date_style" setting.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mweilguni@sime.com
Subject: Re: index over timestamp not being used
In-Reply-To: <200707251505.11182.mweilguni@sime.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox