- "nha" wrote:
>
> Another way could concern the hash join. It has been shown that this
> step costs a lot with respect to the overall runtime. Depending on
> available storage space and DBMS load, a kind of materialized view
> may
> be handled in order to cut off the overloading join. Her
Accidentally sent to nha only
--- On Wed, 7/8/09, John Cheng wrote:
> From: John Cheng
> Subject: Re: [GENERAL] Problem search on text arrays, using the overlaps (&&)
> operator
> To: "nha"
> Date: Wednesday, July 8, 2009, 4:24 PM
> Hi nha,
>
&
Hello,
Le 8/07/09 0:52, John Cheng a écrit :
> I don't mean to be pesky. I was just wondering if there is anything
> else I should try?
>
> Should I simply rewrite all queries, change the form
>
> WHERE textarr && '{foo, bar}'::text[]
>
> To
>
> WHERE (textarr && '{foo}'::text[]
> OR
I don't mean to be pesky. I was just wondering if there is anything
else I should try?
Should I simply rewrite all queries, change the form
WHERE textarr && '{foo, bar}'::text[]
To
WHERE (textarr && '{foo}'::text[]
OR textarr && '{bar}'::text[])
?
--
Sent via pgsql-general maili
- "nha" wrote:
> From: "nha"
> To: "John Cheng"
> Cc: pgsql-general@postgresql.org
> Sent: Monday, July 6, 2009 9:12:22 AM GMT -08:00 US/Canada Pacific
> Subject: Re: [GENERAL] Problem search on text arrays, using the overlaps (&&)
&g
Hello,
Le 2/07/09 2:07, John Cheng a écrit :
We use text[] on one of our tables. This text[] column allows us to
search for records that matches a keyword in a set of keywords. For
example, if we want to find records that has a keyword of "foo" or
"bar", we can use the condition:
keywords&&
e type of problem would affect queries
on tsvector columns, but I have not tested myself.
- Original Message -
From: "Andreas Wenk"
To: "John Cheng" , "PG-General Mailing List"
Sent: Friday, July 3, 2009 2:12:46 AM GMT -08:00 US/Canada Pacific
Subject: Re:
John Cheng schrieb:
---
For some reason, I am seeing a big difference in our real database. I
don't want to just rewrite all of our queries yet. I'm guessing the
data makes a big difference. What would be a good way to examine the
data to figure out what's the best way to write our queri
We use text[] on one of our tables. This text[] column allows us to
search for records that matches a keyword in a set of keywords. For
example, if we want to find records that has a keyword of "foo" or
"bar", we can use the condition:
keywords && '{foo, bar}'::text[]
Another wau is to do this
