X-Original-To: pgsql-sql@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 32771475461 for ; Mon, 17 Feb 2003 05:54:23 -0500 (EST) Received: from serwer.skawsoft.com.pl (serwer.skawsoft.com.pl [213.25.37.66]) by postgresql.org (Postfix) with ESMTP id 9650D474E53 for ; Mon, 17 Feb 2003 05:54:22 -0500 (EST) Received: from klaster.net (pq197.krakow.cvx.ppp.tpnet.pl [213.76.41.197]) by serwer.skawsoft.com.pl (Postfix) with ESMTP id A222F2B742 for ; Mon, 17 Feb 2003 11:45:32 +0100 (CET) Message-ID: <3E50BF12.4020909@klaster.net> Date: Mon, 17 Feb 2003 11:53:06 +0100 From: Tomasz Myrta User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; PL; rv:1.1) Gecko/20020826 X-Accept-Language: pl, en-us, en MIME-Version: 1.0 To: "'pgsql-sql@postgresql.org'" Subject: Special Date/Time Inputs Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/366 X-Sequence-Number: 11764 Hi How do you use Special Date/Time Inputs described in Table 5.14 (Postgresql documentation)? It looks like only now() works. When I try to select epoch() I get error, that such function doesn't exist. Anyway it came from another problem: I have table with millions records indexed on timestamp. I tried to speed up using this table, so I changed timestamp into seconds-since-epoch (integer). What do you think about it? Is there a better way to convert this field back into timestamp than '1970-01-01'::timestamp+cast(field || ' seconds' as interval) ? Regards, Tomasz Myrta