From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: pg_upgrade fails with missing FTS resources |
Date: | 2012-06-16 01:16:47 |
Message-ID: | 20120616011647.GA26006@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Jun 15, 2012 at 04:15:57PM +0100, Daniele Varrazzo wrote:
> Hello,
>
> pg_upgrade fails on missing FTS dictionaries requiring external files.
> --check fails to detect the incompatibility.
>
> E.g. after installed italian_fts (http://pgxn.org/dist/italian_fts/)
> into a database, the pg_upgrade_dump_db.sql contains the command:
>
> CREATE TEXT SEARCH DICTIONARY italian_ispell (
> TEMPLATE = pg_catalog.ispell,
> dictfile = 'italian_ispell', afffile = 'italian_ispell', stopwords
> = 'italian_ispell' );
>
> that fails with a:
>
> psql:/var/lib/postgresql/pg_upgrade_dump_db.sql:56891: ERROR: could
> not open dictionary file
> "/usr/share/postgresql/9.1/tsearch_data/italian_ispell.dict": No such
> file or directory
>
> I think it would be enough to detect the incompatibility at --check
> time, as much as it's done for the required libraries, and only for
> the builtin dict types.
>
> If you want the issue to be fixed I can try to fix it myself: it seems
> easy enough.
Sure, we can test for that. What system column stores these file names?
Do we have any other file references in our system tables?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-06-16 02:27:59 | Re: pg_upgrade fails with missing FTS resources |
Previous Message | Euler Taveira | 2012-06-15 20:22:55 | Re: BUG #6695: PgAdminIII |