Re: [PERFORM] Slow select times on select with xpath

for type xml SQL state: 42883 Robert Haas wrote: > > On Thu, Sep 3, 2009 at 4:06 PM, astro77 wrote: >> I was receiving an error that an XML field does not support the various >> indexes available in postgresql. > > Please post what happens when you try. > >&g

Re: [PERFORM] Slow select times on select with xpath

Thanks Kevin. I thought about using tsearch2 but I need to be able to select exact values on other numerical queries and cannot use "contains" queries. It's got to be fast so I cannot have lots of records returned and have to do secondary processing on the xml for the records which contain the exa

Re: [PERFORM] Slow select times on select with xpath

Sep 3, 2009 at 4:06 PM, astro77 wrote: > I was receiving an error that an XML field does not support the various > indexes available in postgresql. Please post what happens when you try. -- View this message in context: http://www.nabble.com/Slow-select-times-on-select-with-xpath-tp252593

Re: [PERFORM] Slow select times on select with xpath

I was receiving an error that an XML field does not support the various indexes available in postgresql. Is there an example of how to do this properly? Robert Haas wrote: > > On Wed, Sep 2, 2009 at 11:04 AM, astro77 wrote: >> >> I've got a table set up with an XML fie

[PERFORM] Slow select times on select with xpath

I've got a table set up with an XML field that I would like to search on with 2.5 million records. The xml are serialized objects from my application which are too complex to break out into separate tables. I'm trying to run a query similar to this: SELECT serialized_object as outVal