X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D29FE55CC5 for ; Thu, 3 Mar 2005 07:27:52 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 65743-05 for ; Thu, 3 Mar 2005 07:27:51 +0000 (GMT) Received: from mail1.elevating.com (wsip-68-99-77-237.tu.ok.cox.net [68.99.77.237]) by svr1.postgresql.org (Postfix) with ESMTP id 2C34555C0A for ; Thu, 3 Mar 2005 07:27:50 +0000 (GMT) Received: from bretsony.brets.elevating.com (bretsony.brets.elevating.com [10.23.0.139]) by mail1.elevating.com (8.11.6/8.11.6) with ESMTP id j237RPK19031 for ; Thu, 3 Mar 2005 01:27:25 -0600 Subject: Re: definative way to place secs from epoc into timestamp From: Bret Hughes To: postgresql sql list In-Reply-To: <2bf00b6e6300e2c76bc3c09fa89e7913@myrealbox.com> References: <1109780719.28180.86.camel@bretsony> <13089.1109793126@sss.pgh.pa.us> <1109794066.27857.100.camel@bretsony> <13466.1109795186@sss.pgh.pa.us> <1109828560.27905.137.camel@bretsony> <2bf00b6e6300e2c76bc3c09fa89e7913@myrealbox.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-9.7x.1) Date: 03 Mar 2005 01:27:25 -0600 Message-Id: <1109834845.27905.147.camel@bretsony> Mime-Version: 1.0 X-Elevating-MailScanner: Found to be clean X-Elevating-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.423, required 5, BAYES_00 -1.50, TW_PG 0.08) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200503/38 X-Sequence-Number: 20517 On Thu, 2005-03-03 at 00:41, Michael Glaesemann wrote: > > On Mar 3, 2005, at 14:42, Bret Hughes wrote: > > > also my first two pgsql functions :) > > > > cat ts2int.sql > > FWIW, there's a patch in the queue for 8.1 that adds a to_timestamp > function that converts between Unix epoch and timestamp with time zone. > > http://momjian.postgresql.org/cgi-bin/pgpatches2 > > Doesn't help you now, but it'll be there in the future. > Cool. Nice to know I am not the only one. a RFE would be to let to_timestamp be to a timezone without time zone and have a to_timestamptz do the time zone thing. Seems more consistent and would give me the functionality I am looking for :) Bret