Howard News writes:
> On 30/01/2019 18:08, Tom Lane wrote:
>> Note that if you had those functions laying around ever since 8.3,
>> they're probably just "loose" and not wrapped into an extension at all.
> unfortunately running
> create extension tsearch2 from unpackaged;
> caused the following
On 30/01/2019 18:08, Tom Lane wrote:
Note that if you had those functions laying around ever since 8.3,
they're probably just "loose" and not wrapped into an extension at all.
You could fix that in a 9.5 database by running
create extension tsearch2 from unpackaged;
which should be enough
Howard News writes:
> On 30/01/2019 17:20, Adrian Klaver wrote:
>> Is to late to experiment with dropping the extension on a 9.5 database
>> and then dumping?
> Not a problem - The problem only shows in development so far. I have all
> the originals in 9.5 and backups to try this on.
Note
On 30/01/2019 17:20, Adrian Klaver wrote:
Is to late to experiment with dropping the extension on a 9.5 database
and then dumping?
Not a problem - The problem only shows in development so far. I have all
the originals in 9.5 and backups to try this on.
tsearch
functions in my database, and these were copied into the pg_dump that I
restored into v11 and have caused some confusion and problems.
For example, select to_tsquery('english', 'hello') would not work. The
reason is the additional functions, domains etc that were added to the
public
Hi,
upgrading from 9.5 to 11.1, I have a few tsearch problems that appear to
relate to a much older migration (8.3)
Originally, for those that remember that far back, tsearch was a contrib
module. However it appears that I still have some of the old tsearch
functions in my database
