lexem stop or not after stemming, but russian before.
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Please, apply attached patch, it solves the problem.
--
Teodor Sigaev
[EMAIL PROTECTED]
intarray_patch.gz
Description: application/gzip
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Please, apply patch for tsearch to current CVS.
Patch resolve ERROR problem for non-goog query_txt.
Teodor Sigaev wrote:
> Now you can use:
> regression=# select 'the'::mquery_txt;
> ERROR: Your query contained only stopword(s), ignored
> regression=# select 'good&
gt;>rather than irate users ('Your search interface sucks! It keeps
>>crashing!')
>>
>>Oh, well, off to implement some try: catch: logic.
>>
>>Ross
>>
>>---(end of broadcast)---
>>TIP 4: Don
to current CVS, of course. Sorry
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
CHANGES:
August 13, 2002
Use parser of OpenFTS v0.33.
--
Teodor Sigaev
[EMAIL PROTECTED]
tsearch_patch.gz
Description: application/gzip
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Fixed very stupid but important bug: mixing calls of some founctions from
contrib/tsearch and contrib/ltree :)
--
Teodor Sigaev
[EMAIL PROTECTED]
patch_ltree.gz
Description: application/gzip
---(end of broadcast)---
TIP 6: Have you searched
r: parse error at or near ""
Is it normal behaviour? Its seems to me that isn't..
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail c
m lane
>
> ---(end of broadcast)---
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
>
--
Teodor Sigaev
[EMAIL PROTECTED]
---
Tom Lane wrote:
> Teodor Sigaev <[EMAIL PROTECTED]> writes:
>
>>>Hmm, is this patch really correct? Removing the gistadjscans() call
>>>from gistSplit seems wrong to me --- won't that miss reporting splits
>>>on leaf pages? Or does this not matte
Tom Lane wrote:
> Teodor Sigaev <[EMAIL PROTECTED]> writes:
>
>>>Yeah, but the update case is inserting more entries into the index.
>>>I'm wondering if that causes the index scan's state to get corrupted
>>>so that it misses scanning som
Sorry, forgot a patch...
Teodor Sigaev wrote:
>
>
> Oleg Bartunov wrote:
>
>> Just tested with 7.2.1. It works. We have one more patch (for rtree_gist)
>> to submit before 7.2.2 release.
>>
>
> Attached patch fix a bug with creating index. Bug was
Oleg Bartunov wrote:
> Just tested with 7.2.1. It works. We have one more patch (for rtree_gist)
> to submit before 7.2.2 release.
>
Attached patch fix a bug with creating index. Bug was reported by Chris Hodgson
<[EMAIL PROTECTED]>. Please, apply it for 7.2.2 and current CV
Tested it with current CVS. It works.
Oleg Bartunov wrote:
> Just tested with 7.2.1. It works. We have one more patch (for rtree_gist)
> to submit before 7.2.2 release.
>
> Oleg
>
> On Sun, 26 May 2002, Teodor Sigaev wrote:
>
>
>>>Yeah, but the upda
st manages it.
Thank you, Tom. You give me a direction for looking. Attached patch fix
the problem with broken state. Please apply it for 7.2.2 and current cvs
(sorry,
but I'll have a possibility to check it on current cvs only tomorrow).
--
Teodor Sigaev
[EMAIL PROTECTED]
patch_gistupd
s, but brief looking at the differences in the source
>>did not make me conveinced that it was indeed fixed...
>>
>>Anyone knows otherwise?
>>
>>Thanks a lot!
>>
>>Dima
>>
>>
>>---(end of broadcast)---
>>TIP 4: Don't 'kill -9' the postmaster
>>
>>
>
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Hello.
Some example:
compile and install contrib/tsearch module
and now:
wow=# create table foo (bar txtidx);
CREATE
wow=# \d foo
Table "foo"
Column | Type | Modifiers
++---
bar| txtidx | not null
Why field 'bar' has modifier &#x
select * from treetbl where treefld <* '
>
>
> -----------(end of broadcast)---
> TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
>
>
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end
tator. But operator with different types in
argument can't be commutator with itself. So I maked operator ~~ only for
postgres can use index access for operator @@. There is no any difficulties to
adding index support for operator ~~. The same things is with contrib/tsearch
module.
But I think
> It's my mistake, the problem is with locale, I'll send patch as soon as,
> but
> I can't see tsearch in contrib directory (in contrib/README tsearch
> exists) in current cvs. :(
Ok now, I got.
Please apply attached patch for contrib/tsearch.
--
Teo
contrib directory (in contrib/README tsearch exists) in
current cvs. :(
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
data with 1 random values.
Result:
1. Original gist.c
% time psql wow < sql.cmd
psql wow < sql.cmd 0.00s user 0.02s system 0% cpu 7.170 total
2. Patched gist.c
% time psql wow < sql.cmd
psql wow < sql.cmd 0.02s user 0.00s system 2% cpu 0.699 total
We can see that calling fmgr_info
al_function' with execution of sequence
search on library name. Any suggestion?
--
Teodor Sigaev
[EMAIL PROTECTED]
patch_dfmgr.gz
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
idx
> ***
> *** 34,39
> select count(*) from tstmp where t < '2001-05-29 08:33:09+04';
>count
> ---
> ! 7
> (1 row)
>
> --- 34,39 ----
> select count(*) from tstmp where t < '2001-05-29 08:33:09+04';
>
6:15 2001
***
*** 23,28
--- 23,29
#include
#ifdef HAVE_SYS_SEM_H
+ #include
#include
#endif
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
4 MSD 2001
teodor@xor:/usr/src/sys/compile/XOR i386
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
; OB> actually it just needs to wrap a release.
>
> OB> The OpenFTS project web site - http://openfts.sourceforge.net/
>
> Sorry, but I have received:
>
> Not Found
>
> The requested URL / was not found on this server.
>
>
> Apache/1.3.19 Server at openft
Now we don't use gistPageAddItem (
see http://fts.postgresql.org/db/mw/msg.html?mid=118707).
This is our oversight.
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
needs to have function which
return size of key or index_formtuple must looks at GISTENTRY.bytes(
Note: A lot of currrent implementation of GiST modules don't set value
GISTENTRY.bytes ). Or fields in pg_opclass:
int len_key
bool is_lossy_compress
if len_key==-1 then key is varlena type.
--
T
lace
> other than the opclass needed?
>
So, may by add to pg_opclass two fields?
bool is_varlena_key
bool is_lossy_compress
Then index_formtuple must look at is_varlena_key and 'with (islossy)'
could be determined automatically by view at used ops.
--
Te
801 - 830 of 830 matches
Mail list logo
