Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id DA6149FB5A5 for ; Wed, 24 Jan 2007 10:13:45 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 30420-09 for ; Wed, 24 Jan 2007 10:13:30 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.235]) by postgresql.org (Postfix) with ESMTP id 6EE109FB388 for ; Wed, 24 Jan 2007 10:13:30 -0400 (AST) Received: by nz-out-0506.google.com with SMTP id i11so160303nzh for ; Wed, 24 Jan 2007 06:13:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Zvy6YrvT0jZ7nAlTRwfVTNNnKAL5n2GgAyEN07u3s9aupXcxKfwlbcmB92oLZV1t4e59JqrArS5KUYbCTDvs5LhFYvgvASczkAvZyoopJGnSvPtlMnzgBKEVlFE17n/zgnd9n6s3/56w3Gam62Oki9KONDk2hS2s7naTK7xWiUA= Received: by 10.65.210.18 with SMTP id m18mr1224093qbq.1169648007219; Wed, 24 Jan 2007 06:13:27 -0800 (PST) Received: by 10.65.188.5 with HTTP; Wed, 24 Jan 2007 06:13:27 -0800 (PST) Message-ID: Date: Wed, 24 Jan 2007 19:13:27 +0500 From: "Shoaib Mir" To: "Peter Eisentraut" Subject: Re: Install XML on Postgres 8.1 Cc: pgsql-admin@postgresql.org, "Rajesh Kumar Mallah" In-Reply-To: <200701241220.46204.peter_e@gmx.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4164_20522749.1169648007083" References: <45B4A1DA.1080404@yahoo.com.br> <200701240030.45045.peter_e@gmx.net> <200701241220.46204.peter_e@gmx.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/224 X-Sequence-Number: 24380 ------=_Part_4164_20522749.1169648007083 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline The following will explain in detail how Oracle handles the XML data and also the indexing and searching mechanism for it: http://www.oracle.com/technology/oramag/oracle/04-sep/o54xml.html ------------- Shoaib Mir EnterpriseDB (www.enterprisedb.com) On 1/24/07, Peter Eisentraut wrote: > > Shoaib Mir wrote: > > Do we have XML docs indexing mechanism in the todo's for 8.3? as this > > is one of the problem I faced while moving the Oracle like XML > > functionality to PostgreSQL using xml2 contrib. > > Indexing of data types is done in terms of operator classes (or maybe > operator families in 8.3, not sure), but so far no one has proposed to > define any operators whatsoever on the XML type, so I don't see where > any indexing mechanism would come from at the moment. What does Oracle > offer? > > -- > Peter Eisentraut > http://developer.postgresql.org/~petere/ > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster > ------=_Part_4164_20522749.1169648007083 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline The following will explain in detail how Oracle handles the XML data and also the indexing and searching mechanism for it:

http://www.oracle.com/technology/oramag/oracle/04-sep/o54xml.html

-------------
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)

On 1/24/07, Peter Eisentraut < peter_e@gmx.net> wrote:
Shoaib Mir wrote:
> Do we have XML docs indexing mechanism in the todo's for 8.3? as this
> is one of the problem I faced while moving the Oracle like XML
> functionality to PostgreSQL using xml2 contrib.

Indexing of data types is done in terms of operator classes (or maybe
operator families in 8.3, not sure), but so far no one has proposed to
define any operators whatsoever on the XML type, so I don't see where
any indexing mechanism would come from at the moment.  What does Oracle
offer?

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

------=_Part_4164_20522749.1169648007083--