Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f93LE8n15198 for ; Wed, 3 Oct 2001 17:14:08 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f93LE2I11456; Wed, 3 Oct 2001 17:14:02 -0400 (EDT) To: jason.servetar@ccgenesis.com cc: pgsql-sql@postgresql.org Subject: Re: to_date/to timestamp going to BC In-reply-to: <309339290B4FD31184BC0060B06888CB01D0FDF2@CADILLAC> References: <309339290B4FD31184BC0060B06888CB01D0FDF2@CADILLAC> Comments: In-reply-to jason.servetar@ccgenesis.com message dated "Wed, 03 Oct 2001 14:22:10 -0600" Date: Wed, 03 Oct 2001 17:14:02 -0400 Message-ID: <11453.1002143642@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200110/38 X-Sequence-Number: 4993 jason.servetar@ccgenesis.com writes: > Can someone tell me if this is a bug with the date functions or am I using > them incorrectly? I get the right thing when I use the right format: regression=# select dt, to_timestamp(dt, 'FMMonth dd, yyyy') from test_date; dt | to_timestamp ----------------+------------------------ March 11, 1997 | 1997-03-11 00:00:00-05 (1 row) However, I'd agree that this shows a lack of robustness in to_timestamp; it's not objecting to data that doesn't match the format. regards, tom lane