--Qxx1br4bt0+wmkIi
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

On Thu, Nov 03, 2005 at 03:12:33PM +0000, Bernhard Weisshuhn <bkw (AT) weisshuhn (DOT) de> wrote:

Teodor Sigaev sent me a patch even before the web submission got past
the moderators! Not only is tsearch2 quick, its developers are, too!
;-)

The attached patch for Teodor seems to fix the problem for me. I say
'seems' since my testings conditions differ a bit from the ones the
problem appeared, but I did test the same set of queries.

cheers everybody,
Bernhard Weißhuhn

--Qxx1br4bt0+wmkIi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="tsearch2-RNHDRSZ.patch"

*** postgresql-8.1RC1/contrib/tsearch2/ispell/regis.h.orig Thu Nov 3 20:41:27 2005
--- postgresql-8.1RC1/contrib/tsearch2/ispell/regis.h Thu Nov 3 21:06:48 2005
***************
*** 13,19 ****
unsigned char data[1];
} RegisNode;

! #define RNHDRSZ (sizeof(uint32)+sizeof(void*))

#define RSF_ONEOF 1
#define RSF_NONEOF 2
--- 13,19 ----
unsigned char data[1];
} RegisNode;

! #define RNHDRSZ (offsetof(RegisNode,data))

#define RSF_ONEOF 1
#define RSF_NONEOF 2

--Qxx1br4bt0+wmkIi
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

--Qxx1br4bt0+wmkIi--

Bernhard Weisshuhn wrote:

I meant 'from' of course ;-)

--bkw

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend