---(end of broadcast)---
TIP 8: explain analyze is your friend
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http
-
PostgreSQL 7.4 on i386-unknown-freebsd5.1, compiled by GCC gcc (GCC) 3.2.2
[FreeBSD] 20030205 (release)
(1 row)
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet
runtime: 0.047 ms
(2 rows)
Several thousands?
Tom Lane wrote:
Teodor Sigaev [EMAIL PROTECTED] writes:
Explain analyze takes 3 times more time for execution. Why?
Measurement overhead. It would seem your platform has a particularly
slow version of gettimeofday() though ... I've never noticed
... If you mean rows in Seq Scan than
gettimeofday was called (52936+1)*2. Huge value :(
Tom Lane wrote:
Teodor Sigaev [EMAIL PROTECTED] writes:
How many times is gettimeofday called?
Twice per plan node visit, if you are doing EXPLAIN ANALYZE. (The
number of visits is one more than the number
is a bulk upload.
2 If word is frequent then query with 'IN (select * from func()) may works slow...
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once
dictionary, which can define language and normalize word...
Look at default_russian configuration of tsearch2 and read more about tsearch2.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1
stat('select TSVECTOR from TABLE') order by ndoc desc, nentry
desc, word;
Where TSVECTOR is name of column of tsvector type and TABLE is a table with
that column.
Warn: it works very slow.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
---(end
on textdate (or some other
suitable datum)
2 If word is frequent then query with 'IN (select * from func()) may works slow...
if it is often too slow then creating a temp table and doing a plain
join may be faster.
Table structure as indidx decrease this problem.
--
Teodor Sigaev
(super-imposed) signatures of childs.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere
it?
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
can I solve this problem ?
Is it a limitation of PostgreSQL or the R-Tree concept ?
Thank you in advance.
Márcio Caetano.
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
--
Teodor Sigaev
be quiet.
--
Teodor Sigaev E-mail: [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])
-than' one. Is it?
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
to support this.
Its only union and picksplit user-defined methods in contrib modules.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister
*entryvec, int *size)
Datum picksplit(int32 n, GISTENTRY *entryvec, GIST_SPLITVEC *v)
It seems to me that first case is clearer. Of course, I change all contrib
modules to new interface.
What do you think?
--
Teodor Sigaev E-mail: [EMAIL PROTECTED
Ok, I just commited changes, pls, check it on HPPA.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail
This is small README fix for contrib/intarray. Thank you.
--
Teodor Sigaev
[EMAIL PROTECTED]
intarray_patch.gz
Description: application/gzip
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
95.07% 93.65% psql
postmaster doesn't take a CPU time...
--
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])
:/usr/src/sys/compile/XOR i386
--
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])
Peter Eisentraut wrote:
Teodor Sigaev writes:
wow=# select 5.3::float;
ERROR: Bad float8 input format '5.3'
Does it accept '5,4'::float?
Yes, it accepted '5,4'::float format.
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
--
Teodor Sigaev
[EMAIL PROTECTED
)
It seems to me that it's mistake. ISALNUM shoud define correct character in
name of node (level). Try to test
with incorrect ltree value 'a..b'.
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
prepare cumulative patch.
Nevertheless, we have no chance to insert this to 7.3 release :(. Only for
7.3.1 or even 7.4.
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http
REATE INDEX my_idx ON test USING
gist(txt2txtidx(a)) may decreas performance :(
2 OpenFTS. We wanted that txtidx works with OpenFTS. And adding dictionaries,
txt2txtidx, trigger, type mquery_txt etc
was an experiment.
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end
in __libc_start_main () from /lib/i686/libc.so.6
Magnus
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast
Teodor Sigaev wrote:
Does it crashed?
# select txt2txtidx('Can - Live 1971-77');
Line txtidx.c:366 :
lemm = lemmatize(token, lenlemm, type);
lemmatize() is defined in morph.c. Did you use another modules for
postgresql?
It seems to me that we see a name conflict. Function lemmatize
. Just only full reinstall (with initdb and rm -rf
/usr/local/pgsql) postgresql...
Can you give me login on you computer for a several hours?
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once
with it.
So you tsearch guys will have to work it out :)
--
Teodor Sigaev
[EMAIL PROTECTED]
tsearch_patch.gz
Description: application/gzip
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
@@
{
if (i != 0)
{
- *ptr = NODE_DELIMITER;
+ *ptr = '.';
ptr++;
}
if (curqlevel-numvar)
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast
This patch fixes minor bugs in dictionary generator in contrib/tsearch
(contrib/tsearch/makedict/makedict.pl)
Thank you.
--
Teodor Sigaev
[EMAIL PROTECTED]
tsearch_patch.gz
Description: application/gzip
---(end of broadcast)---
TIP 4: Don't
for 7.4
Thank you.
--
Teodor Sigaev
[EMAIL PROTECTED]
ltree_73.patch.gz
Description: application/gzip
ltree_74.patch.gz
Description: application/gzip
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
/postgres/gist/tsearch/V2/tsearch.tar.gz
It should works with 7.3 and current CVS.
Any comments please send to Oleg Bartunov ([EMAIL PROTECTED]) and
Teodor Sigaev ( [EMAIL PROTECTED] ).
I'm going to vacation until March, so don't fill my mailbox :-)
Regards,
Oleg
But in all this places returned value doesn't used, just pfree'ed (except
./access/heap/tuptoaster.c
where it's checked with NULL).
Q: why? why isn't it a bool value?
Is there some idea which I havn't see?
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast
that there was some other piece
of information that the index AM should return, we'd have to change
right back to returning a struct...
Agreed.
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once
to Oleg Bartunov ([EMAIL PROTECTED]) and
Teodor Sigaev ( [EMAIL PROTECTED] ).
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
a bug?
Must be 'internal'. It's not a bug :) because this function is GiST interface
member
and itsn't any nessesarity to call it by hand.
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
, dentry-key, r, page,
offsetNumber, dentry-bytes, FALSE);
Isn't the call missing the isNull parameter?
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL
=0x82adf88) at postgres.c:897
#11 0x081619f0 in PostgresMain (argc=4, argv=0x82960c0, username=0x82966c0 postgres)
at postgres.c:2013
#12 0x08110625 in main (argc=4, argv=0xbc14) at main.c:235
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast
Hi!
xor% uname -a
FreeBSD xor 5.0-RELEASE FreeBSD 5.0-RELEASE #7: Thu Mar 6 21:53:07 MSK 2003
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/XOR i386
xor% gcc -v
Using built-in specs.
Configured with: FreeBSD/i386 system compiler
Thread model: posix
gcc version 3.2.1 [FreeBSD] 20021119 (release)
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
, 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_gistupdate.gz
Description: GNU Zip
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 update case is inserting more entries into the index
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 CVS.
--
Teodor Sigaev
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 reported by Chris
Hodgson [EMAIL PROTECTED]. Please
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 some entries.
Thank you, Tom. You give me a direction for looking
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 matter for some reason?
gistadjscans() is moving
command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL
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 command to [EMAIL PROTECTED] so that your
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
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
to current CVS, of course. Sorry
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
, 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
TABLE_DICT_END
dict/russian_stemming.dct:
TABLE_DICT_START
ru_RU.KOI8-R,
NULL,
NULL,
ru_RUKOI8R_stem,
ru_RUKOI8R_is_stopword,
NULL
TABLE_DICT_END
So english stemmer defines is lexem stop or not after stemming, but russian before.
--
Teodor
integer
from pointer without a cast
copy.c:1130: too many arguments to function `coerce_type_constraints'
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send
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.
--
Teodor Sigaev
[EMAIL PROTECTED
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.
--
Teodor Sigaev
[EMAIL
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]
--- 23,29
#include errno.h
#ifdef HAVE_SYS_SEM_H
+ #include sys/types.h
#include sys/sem.h
#endif
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org
(1 row)
--- 34,39
select count(*) from tstmp where t '2001-05-29 08:33:09+04';
count
---
! 66
(1 row)
--
Teodor Sigaev
[EMAIL PROTECTED]
patch_btreesql.gz
---(end of broadcast)---
TIP 6: Have you
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
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 for 7 times may be very expensive.
--
Teodor Sigaev
[EMAIL PROTECTED]
ugly_patch.gz
---(end of broadcast
. 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 that there is not any other necessity in presence ~~.
--
Teodor Sigaev
[EMAIL
. :(
--
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])
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.
--
Teodor Sigaev
[EMAIL PROTECTED
* '
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through
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 'not null'?
--
Teodor
7: don't forget to increase your free space map settings
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
---(end
, e=0x40110cd8,
tinfo=0x7afff594) at btree_utils_var.c:220
[ gdb gets confused here, possibly stack is smashed ]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
--
Teodor
I tried running 'make installcheck' in contrib just now, and didn't
get past btree_gist :-(
Fix and test on Alpha box.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
---(end of broadcast)---
TIP 8: explain analyze is your
of results. It seems to me this information may be helpful for query
optimizer, so, is there way to say it to optimizer?
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
---(end of broadcast)---
TIP 7: don't forget
);
return RecPtr;
}
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
---(end of broadcast)---
TIP 6: Have you searched our list archives
.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
into the core --- but the case for
it would be stronger if it worked correctly ...
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
---(end of broadcast
We can make r-tree as contrib module and then we will have example of index in
contrib...
By integrating the opclasses needed to replace R-tree, we can start
down the path to deprecating and eventually removing R-tree.
--
Teodor Sigaev E-mail: [EMAIL
FYI, compress and decompress methods may be trivial.
For GiST you still need 7 support functions + the operator function,
some of which aren't exactly simple to implement, the picksplit for
instance.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED
framework, becouse it is about heap pages. I
suspect trap occurs while concurrent vacuum, but I am not sure.
PS
My concurrency testing scripts:
http://www.sigaev.ru/gist/
concur.pl - generator of SQL statements
concur.sh - simple wrapper about concur.pl which reinit db, makes db and table.
--
Teodor
multibyte encoding and has problems with UTF :(.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
---(end of broadcast)---
TIP 5: Have you checked
are unique the the later keys will not be compared ;)
2. About rtree interface: it's possible to write GiST-RTree layer compatibility
interface. User's interface will just copied from RTree, and layer will
translate it to GiST interface.
--
Teodor Sigaev E-mail
feature freeze), if you don't find
the cause beforehand.
It's definitly bug in a vaccum code, I got the same trap without any GiST
indexes (to reproduce, just comment out 'create index' command in my script).
--
Teodor Sigaev E-mail: [EMAIL PROTECTED
Sorry, fixed.
Qingqing Zhou wrote:
Teodor Sigaev [EMAIL PROTECTED] writes
concur.pl - generator of SQL statements
retrieving it is forbidden ...
Regards,
Qingqing
---(end of broadcast)---
TIP 7: don't forget to increase your free space
, Line: 2766)
LOG: server process (PID 15847) was terminated by signal 6
It's definitly bug in a vaccum code, I got the same trap without any GiST
indexes (to reproduce, just comment out 'create index' command in my script).
--
Teodor Sigaev E-mail: [EMAIL
in the contrib/rtree_gist) ?
8.1 pgsql has short lived memory context during index creation which resets
after every insert. 8.0 hasn't this feature, so user-defined function (GiST
interfface) should carefully clean memory.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED
In other words ... if you can test this ... HELP!!!
I'll run tests.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
---(end of broadcast
SQL
statements without any failure. Tests runs on two boxes: PIII/1133MHz adn Quad
Xeon/500MHz and works with four threads.
Further I'm going to increase concurrency up to 12 parallel threads.
PS GiST passed this tests too.
--
Teodor Sigaev E-mail: [EMAIL
Further I'm going to increase concurrency up to 12 parallel threads.
All is ok, test is passed with approximatly 40 millions statements
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru
was wrote to test GiST concurrency.
I suspect it's needed to make some changes in generator to increase number of
updates and vacuums for your goal.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http
http://archives.postgresql.org/pgsql-patches/2005-08/msg00304.php
Could you perhaps test this patch as well, while you already have a
setup for testing parallel vacuums under big loads ?
I didn't find any problem with your patch during testing with 1e8 statements...
--
Teodor Sigaev
Finded problem in GiST isn't too simple to resolve. I'm working on it. The
problem is about update query...
Tom Lane wrote:
Teodor Sigaev [EMAIL PROTECTED] writes:
http://www.sigaev.ru/gist/concur.pl
http://www.sigaev.ru/gist/concur.sh
BTW, these scripts seem to indicate that there's
Fixed in 8.0, 7.4 and 7.3 branches.
Tom Lane wrote:
Teodor Sigaev [EMAIL PROTECTED] writes:
http://www.sigaev.ru/gist/concur.pl
http://www.sigaev.ru/gist/concur.sh
BTW, these scripts seem to indicate that there's a GIST or
contrib/intarray problem in the 8.0 branch. I was trying to use
a from wow where a @ '{1,2,3}' and not a @ '{101}';
After update query select must not find any rows, but it did. The problem was in
GiST code and so any GiST idexes was affected.
Can you say more about your trouble?
--
Teodor Sigaev E-mail: [EMAIL PROTECTED
test suite or more information I'm helpless.
How often do updates/inserts of table and/or ltree column occurs? Vacuum?
Might this be somehow related to the intarray bugs?
No, except case when you update your table something like to:
update tbl set ltreefield=... where ltreefield ...;
--
Teodor
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
---(end of broadcast
into variables
After reconnecting to database all is ok. Is it supposed behaviour?
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
---(end of broadcast
)
Filter: (fts @@ '''foo'''::tsquery)
Why planner suppose that t 'table' will return 1000 rows? Obviosly that function
returns only one value because of itsn't marked as 'returns setof'.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED
in pgsql) can store tree likes to R-tree or B-tree (with
some limitations, such as now pgsql's GiST doesn't support order).
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru
Hi!
8.1 had been tagged, may I develope/commit new tsearch2 code in HEAD branch?
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
---(end of broadcast
#21 0x081957aa in PostmasterMain (argc=3, argv=0x8344788) at postmaster.c:943
#22 0x08158b49 in main (argc=3, argv=0x8344788) at main.c:256
--
22:06:46 up 36 days, 14:41, 7 users, load average: 2.22, 2.55, 3.26
Linux 2.6.5-02 #8 SMP Mon Jul 12 21:34:44 MDT 2004
--
Teodor Sigaev
this conversation be continued there?
PGSphere or not it's unknown for now. Can you prepare minimalist test suite
reproducing problem?
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru
; /* Union of keys in spl_right */
It's very like that spl_right contains correct spl_nright value (0xdb = 219)
and spl_nright contains correct spl_rdatum (pointer 138286924 = 0x83e174c)
--
Teodor Sigaev E-mail: [EMAIL PROTECTED
1 - 100 of 812 matches
Mail list logo
