From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Viliam Ďurina <viliam(dot)durina(at)kios(dot)sk> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: share directory on windows |
Date: | 2011-03-22 15:03:43 |
Message-ID: | 12889.1300806223@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
=?UTF-8?B?VmlsaWFtIMSOdXJpbmE=?= <viliam(dot)durina(at)kios(dot)sk> writes:
> I wanted to install text search dictionaries on Windows 8.4 installation with the following command:
> CREATE TEXT SEARCH DICTIONARY skspell
> (template=ispell, dictfile = slovak_utf8, afffile=slovak_utf8, stopwords=slovak_utf8);
> but got this error:
> ERROR: could not open dictionary file "/usr/share/postgresql/8.4/tsearch_data/slovak_utf8.dict": No such file or directory
That's pretty bizarre. Did you move the postgres executable relative to
the tsearch_data files? It looks like you could get a hard-wired path
if you moved the executable out of its intended place. It's still not
too clear to me why you got *that* hard-wired path though; I'd have
expected the built-in value to be something different from that in a
Windows build. Whose build are you using?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2011-03-22 16:07:32 | Re: Weird problems with C extension and bytea as input type |
Previous Message | Adrian Schreyer | 2011-03-22 13:22:23 | Weird problems with C extension and bytea as input type |