From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Gunnlaugur Thor Briem <gunnlaugur(at)gmail(dot)com> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: unaccent(text) fails depending on search_path (WAS: pg_upgrade fails saying function unaccent(text) doesn't exist) |
Date: | 2018-09-05 19:03:33 |
Message-ID: | 12109.1536174213@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Gunnlaugur Thor Briem <gunnlaugur(at)gmail(dot)com> writes:
> SET search_path = "$user"; SELECT public.unaccent('foo');
> SET
> ERROR: text search dictionary "unaccent" does not exist
Meh. I think we need the attached, or something just about like it.
It's barely possible that there's somebody out there who's relying on
setting the search path to allow choosing among multiple "unaccent"
dictionaries. But there are way more people whose functions are
broken due to the recent search-path-tightening changes.
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
avoid-depending-on-search-path-in-unaccent.patch | text/x-diff | 1.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2018-09-05 19:04:25 | Re: Max number of WAL files in pg_xlog directory for Postgres 9.2 version |
Previous Message | Michael Paquier | 2018-09-05 18:15:45 | Re: scram-sha-256 authentication broken in FIPS mode |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Gierth | 2018-09-05 19:05:31 | Re: Bug fix for glibc broke freebsd build in REL_11_STABLE |
Previous Message | Andrew Gierth | 2018-09-05 19:01:05 | Re: Bug fix for glibc broke freebsd build in REL_11_STABLE |