Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 9EB424762A8 for ; Fri, 27 Sep 2002 12:01:19 -0400 (EDT) Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id 0E3ED475E2E for ; Fri, 27 Sep 2002 12:01:18 -0400 (EDT) Received: from [63.195.55.98] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.9) with HTTP id 1731878 for ; Fri, 27 Sep 2002 09:01:27 -0700 From: "Josh Berkus" Subject: Re: Date/Time types To: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.5.9 Date: Fri, 27 Sep 2002 09:01:27 -0700 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/379 X-Sequence-Number: 9656 Seb, > I'm french, so excuse me if my english is not correct. Whereas if you were a native English speaker, you would realize that there is no such thing as "correct English" .... > I'd like to create a table with a Timestamp row (named date for > example) and > width a resolution as smaller as possible (1 microsecond if > possible). > > What is exactly the correct query for that question ? > > The query I've written is : > CREATE TABLE "table" ( > "id" int4 NOT NULL, > "date" timestamp [13] NOT NULL ) Sorry, the syntax above creates a table with an *array* of 13 timestamp values. I don't know what the syntax you want for an extra-precision timestamp is. Assuming there is one at all, which there may not be ... I'd also advise against creating tables with reserved words (such as "date" ) as column names. It can cause you all kinds of headaches later on, -Josh Berkus