Received: from yertle.kciLink.com (yertle.kcilink.com [216.194.193.105]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f7GKocP33262 for ; Thu, 16 Aug 2001 16:50:38 -0400 (EDT) (envelope-from khera@kciLink.com) Received: from onceler.kciLink.com (onceler.kciLink.com [216.194.193.106]) by yertle.kciLink.com (Postfix) with ESMTP id 095162E460; Thu, 16 Aug 2001 16:50:32 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.11.4/8.11.4) id f7GKoW898204; Thu, 16 Aug 2001 16:50:32 -0400 (EDT) (envelope-from khera) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15228.12818.456195.792923@onceler.kciLink.com> Date: Thu, 16 Aug 2001 16:50:26 -0400 To: "Josh Berkus" Cc: pgsql-sql@postgresql.org Subject: Re: Re: Interval FAQ - please review In-Reply-To: References: X-Mailer: VM 6.92 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-Archive-Number: 200108/220 X-Sequence-Number: 4452 >>>>> "JB" == Josh Berkus writes: >> Those docs are lacking an explanation that there is no such thing in >> PostgreSQL as a timestamp *without* time zone. JB> Hmmm .... OK, I'll revise the A: but I *don't* want to go into Time Zone JB> issues in this intro. Any docs I can link to? The only good explanation came from the mailing list, from Tom Lane, naturally ;-). Basically, nobody wants to change it, and using a view or a client-side function to strip the timezone info is the way to do it.