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-hackers(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 22:37:00 |
Message-ID: | 22723.1536187020@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
[ redirecting to pgsql-hackers ]
I wrote:
> 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.
Here's a slightly more efficient version.
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
avoid-depending-on-search-path-in-unaccent-2.patch | text/x-diff | 1.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Finzel | 2018-09-06 05:17:02 | Re: PostgreSQL intenal scheduler? |
Previous Message | Thiemo Kellner | 2018-09-05 22:04:58 | Re: PostgreSQL intenal scheduler? |
From | Date | Subject | |
---|---|---|---|
Next Message | Chapman Flack | 2018-09-05 22:38:01 | Re: *_to_xml() should copy SPI_processed/SPI_tuptable |
Previous Message | Daniel Wood | 2018-09-05 22:32:40 | Re: On the need for a snapshot in exec_bind_message() |