On 30/07/2018 16:51, Tom Lane wrote:
> Achilleas Mantzios <achill@matrix.gatewaynet.com> writes:
>> This is with PostgreSQL 10.4.
>> How to reproduce :
>> dynacom=# ALTER ROLE amura3 SET search_path TO "$user", amuragents, public;
>> ALTER ROLE
>> ...
>> dynacom=> show search_path ;
>> search_path
>> ---------------------------
>> $user, amuragents, public
>> (1 row)
> Hm, that's not happening for me:
You (and Adrian) are right. This is due to our own tweaking (which I had forgotten). Sorry for the false alarm.
>
> regression=# alter user joe set search_path to "$user", public;
> ...
> regression=> show search_path ;
> search_path
> -----------------
> "$user", public
> (1 row)
>
> and then pg_dumpall produces
>
> ALTER ROLE joe SET search_path TO "$user", public;
>
> There was a relevant bug fix in March (commit 742869946) ...
> are you certain this is a 10.4 server, and not 10.3 or older?
>
> regards, tom lane
>
--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt
