Yep, a neater workaround for sure!
Cheers,
Gulli
On Wed, Sep 5, 2018 at 2:00 PM Adrian Klaver
wrote:
> On 09/05/2018 01:49 AM, Gunnlaugur Thor Briem wrote:
> > OK, I found the cause of the unaccent dictionary problem, and a
> workaround.
> >
> > It's not the vacuu
OK, I found the cause of the unaccent dictionary problem, and a workaround.
It's not the vacuumdb version, not the unaccent version, and it's not even
a pg_upgrade problem: I get this error also with PG 9.4.18 running on the
old cluster, with both the 10.5 vacuumdb and the 9.4.18 vacuumdb, and I g
+--+-++-
public | unaccent | public.unaccent | rules = 'unaccent' |
(1 row)
Cheers,
Gulli
On Thu, Aug 30, 2018 at 1:48 PM Adrian Klaver
wrote:
> On 08/30/2018 02:24 AM, Gunnlaugur Thor Briem wrote:
> > Thank you! That go
| regdictionary, text | normal |
stable | safe | gthb | invoker | | c|
unaccent_dict |
public | unaccent | text | text| normal |
stable | safe | gthb | invoker | | c |
unaccent_dict |
(2 rows)
Any tips?
Che
Hi,
I'm trying to upgrade an old PG 9.4 cluster to PG 10, and it's failing on
creating an index that uses the unaccent(text) function.
That function is part of the unaccent extension, which is installed in the
old DB cluster. I expect pg_upgrade to create that extension as part of the
upgrade. It
