Jan Urbański wrote:
Great, I didn't know the API was that convenient in 8.3. I'll try
posting a working patch for 8.3 during the weekend.
Here's the patch for 8.3beta2. As was suggested I added a configuration
parameter to the 'simple' dictionary called AcceptAll so now it can work
in two
This bit should be replaced with defGetBoolean. Otherwise it looks
reasonably sane.
Fixed that, thank you.
Regards,
Jan Urbanski
--
Jan Urbanski
GPG key ID: E583D7D2
ouden estin
diff -Naur postgresql-8.3beta2-orig/doc/src/sgml/textsearch.sgml
Tom Lane wrote:
ITAGAKI Takahiro [EMAIL PROTECTED] writes:
-((double) (int32) (recptr.xrecoff -
ckpt_start_recptr.xrecoff)) / XLogSegSize) /
+((double) recptr.xrecoff - (double) ckpt_start_recptr.xrecoff)
/ XLogSegSize) /
Surely this makes matters worse, not
Heikki Linnakangas wrote:
Tom Lane wrote:
ITAGAKI Takahiro [EMAIL PROTECTED] writes:
- ((double) (int32) (recptr.xrecoff -
ckpt_start_recptr.xrecoff)) / XLogSegSize) /
+ ((double) recptr.xrecoff - (double)
ckpt_start_recptr.xrecoff) / XLogSegSize) /
Surely this makes matters
Zdenek Kotala wrote:
Zdenek Kotala wrote:
Zdenek Kotala wrote:
Attached patch removes pg_dump dependency on postgres.h. The main reason
for that was discussed there:
http://archives.postgresql.org/pgsql-hackers/2007-10/msg01261.php
I found two problems there. One is that I forgot
Alvaro Herrera wrote:
Zdenek Kotala wrote:
Zdenek Kotala wrote:
Zdenek Kotala wrote:
Attached patch removes pg_dump dependency on postgres.h. The main reason
for that was discussed there:
http://archives.postgresql.org/pgsql-hackers/2007-10/msg01261.php
I found two problems there. One is
Zdenek Kotala wrote:
Alvaro Herrera wrote:
3) Put following fake into keyword.c before include parse.h line. It
is easiest way.
#define TYPE_IS_DECLARED 1
#define YYLTYPE_IS_DECLARED 1
#define YYLTYPE void*
#define YYSTYPE void*
New version of patch is attached. I selected variant 3 as a
Alvaro Herrera wrote:
Zdenek Kotala wrote:
Alvaro Herrera wrote:
3) Put following fake into keyword.c before include parse.h line. It
is easiest way.
#define TYPE_IS_DECLARED 1
#define YYLTYPE_IS_DECLARED 1
#define YYLTYPE void*
#define YYSTYPE void*
New version of patch is attached. I
Alvaro Herrera [EMAIL PROTECTED] writes:
Zdenek Kotala wrote:
What do you mean not very portable? What could be problem there?
I'm not sure. My point is that it seems your parse.h requires
TYPE_IS_DECLARED, but mine doesn't. What else could be lurking in there
that requires a specific fix?
Tom Lane wrote:
This patch:
http://archives.postgresql.org/pgsql-patches/2007-11/msg00137.php
seems simple and useful enough that I think we ought to slip it into
8.3, even though we are far past feature freeze.
As the simple dictionary type stands in CVS HEAD, it is only useful as
the
Zdenek Kotala [EMAIL PROTECTED] writes:
TYPE_IS_DECLARED was my mistake. It should be YYSTYPE_IS_DECLARED. It
works because YYSTYPE is also defined and #ifdef checks both. Copy and
paste :( error. Sorry for confusion. I'm going to send new version.
[ after further review... ]
It looks to me
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Zdenek Kotala wrote:
What do you mean not very portable? What could be problem there?
I'm not sure. My point is that it seems your parse.h requires
TYPE_IS_DECLARED, but mine doesn't. What else could be lurking in there
that
Oleg Bartunov [EMAIL PROTECTED] writes:
On Wed, 14 Nov 2007, Tom Lane wrote:
One thought that came to mind is that the option name should be just
Accept not AcceptAll. To me All implies that it would accept
*everything* ... including stopwords.
wait, I remind the problem with filters. How
On Wed, 14 Nov 2007, Tom Lane wrote:
Oleg Bartunov [EMAIL PROTECTED] writes:
Let's consider one example - removing accents.
In the past I always recommend people to use regex functions before
to_tsvector conversion to remove accents, but recently I was noticed that
such trick doesn't work with
=?UTF-8?B?SmFuIFVyYmHFhHNraQ==?= [EMAIL PROTECTED] writes:
This bit should be replaced with defGetBoolean. Otherwise it looks
reasonably sane.
Fixed that, thank you.
Applied with minor revisions (changed the parameter name, avoided
probably-insignificant memory leak).
On Wed, 14 Nov 2007, Tom Lane wrote:
Oleg Bartunov [EMAIL PROTECTED] writes:
On Wed, 14 Nov 2007, Tom Lane wrote:
One thought that came to mind is that the option name should be just
Accept not AcceptAll. To me All implies that it would accept
*everything* ... including stopwords.
wait, I
On Wed, 14 Nov 2007, Tom Lane wrote:
Oleg Bartunov [EMAIL PROTECTED] writes:
On Wed, 14 Nov 2007, Tom Lane wrote:
Huh? This is just an option for the simple dictionary, it's got
nothing to do with thesaurus AFAICS.
I can assign simple dictionary as a normalization dictionary for thesaurus
ITAGAKI Takahiro [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] wrote:
Surely this makes matters worse, not better. What happens near a segment
boundary crossing?
Here is the dumped progres information by the attached patch
(only for debug purpose).
Oh, I take that back. I was
On Nov 9, 2007, at 5:24 AM, Magnus Hagander wrote:
On Tue, 2007-11-06 at 18:10 -0800, Henry B. Hotz wrote:
On Nov 6, 2007, at 6:27 AM, Magnus Hagander wrote:
On Fri, Nov 02, 2007 at 11:23:30AM -0700, Henry B. Hotz wrote:
I'm not entirely sure what the intended semantics of
krb_match_realm
Simon Riggs [EMAIL PROTECTED] writes:
Short patch to clarify the name of the column used for the text search
index example, so everybody is clear it is a column name.
Applied, thanks.
regards, tom lane
---(end of
Oleg Bartunov [EMAIL PROTECTED] writes:
On Wed, 14 Nov 2007, Tom Lane wrote:
Huh? This is just an option for the simple dictionary, it's got
nothing to do with thesaurus AFAICS.
I can assign simple dictionary as a normalization dictionary for thesaurus
Sure. So what? You wouldn't use this
21 matches
Mail list logo
