Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA31028 for ; Fri, 25 Feb 2000 11:56:53 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id LAA23872; Fri, 25 Feb 2000 11:54:40 -0500 (EST) From: Bruce Momjian Message-Id: <200002251654.LAA23872@candle.pha.pa.us> Subject: Re: [SQL] how to create index on timestamp field in pre v7 database In-Reply-To: <7601.951496156@sss.pgh.pa.us> from Tom Lane at "Feb 25, 2000 11:29:16 am" To: Tom Lane Date: Fri, 25 Feb 2000 11:54:40 -0500 (EST) CC: Moray McConnachie , pgsql-sql@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL72 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > "Moray McConnachie" writes: > > Agreed - but note that pg_dump currently produces CREATE INDEX > > statements with opclasses included. > > Right, as it should since its purpose is to ensure you rebuild exactly > the same database. I was just opining that handwritten CREATE INDEXes > usually can omit the opclass. (BTW, I fixed the problem with functional > indexes needing an explicit opclass spec last night.) > > > That means running a script created by pg_dump v.6.5.x will fail under > > 7.0 because there is no index opclass of the type datetime? > > An embarrassing problem. We are going to work around this by having > the 7.0 parser discard the word "datetime" if it sees it in the opclass > position. There are a couple of other now-dead opclass names that will > be discarded in the same way. Klugy, but it will get the job done for > reading old dump files. > > (This hack is not in 7.0beta1, but will be in beta2.) It is my understanding we are generating a new beta every night, so it should be there now. -- Bruce Momjian | http://www.op.net/~candle pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026