X-Original-To: pgsql-sql@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id C4EF34762F6 for ; Wed, 5 Mar 2003 10:39:31 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 79592-04 for ; Wed, 5 Mar 2003 10:39:26 -0500 (EST) Received: from ns2.boxsoft.com (dsl092-062-212.lax1.dsl.speakeasy.net [66.92.62.212]) by postgresql.org (Postfix) with ESMTP id D0EA04793CA for ; Tue, 4 Mar 2003 20:37:41 -0500 (EST) Received: from 3eye.boxsoft.com (3eye.boxsoft.com [66.92.62.215]) by ns2.boxsoft.com (8.12.8/8.12.8) with ESMTP id h251btmG000325 for ; Tue, 4 Mar 2003 17:37:55 -0800 Received: from 3eye.boxsoft.com (localhost [127.0.0.1]) by 3eye.boxsoft.com (8.12.8/8.12.8) with ESMTP id h251dguL020732 for ; Tue, 4 Mar 2003 17:39:42 -0800 Received: (from patrick@localhost) by 3eye.boxsoft.com (8.12.8/8.12.8/Submit) id h251dgTw020731 for pgsql-sql@postgresql.org; Tue, 4 Mar 2003 17:39:42 -0800 Date: Tue, 4 Mar 2003 17:39:42 -0800 From: patrick To: pgsql-sql@postgresql.org Subject: upgrading from 7.1.2 to 7.3.2 Message-ID: <20030304173942.Z4392@3eye.boxsoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Virus-Scanned: by amavisd-new X-Archive-Number: 200303/160 X-Sequence-Number: 12200 Greetings, I've just upgraded from PostgreSQL 7.1.2 to 7.3.2. Things seem to work OK so far (only been about 70 min or so since upgrade). One thing I did see break is how I've been using timestamp(): e.g., in 7.1.2 => select timestamp ( 1046923200 ); timestamp ------------------------ 2003-03-05 20:00:00-08 (1 row) in 7.3.2 => select timestamp ( 1046923200 ); ERROR: TIMESTAMP(1046923200) precision must be between 0 and 6 Can anyone point me to a work-around? Thanks in advance, sidster -- They who would sacrifice freedom for security will have neither. -Ben Franklin