Re: search_path update weirdness

Date: Mon, 8 Jul 2013 14:46:29 +0200
Subject: Re: [ADMIN] search_path update weirdness
From: mabewlun(at)gmail(dot)com
To: colin_sloss(at)hotmail(dot)com
CC: pgsql-admin(at)postgresql(dot)org

Hi szymon,
My mistake. I chock it up to another manic monday.
Thanks!
Colin

On 8 July 2013 14:40, Colin S <colin_sloss(at)hotmail(dot)com> wrote:

Hello,
I made a bad update to search_path, which basically had line returns:
prod_candidate=# alter user postgres set search_path to 'search_path=public, schem
prod_candidate'# a1, schema2, schema3'prod_candidate-# ;ALTER ROLE

And now, I can't get it to insert correctly again, there always seems to be some backslashes stuck in there:

prod_candidate=# alter user postgres set search_path to '';ALTER ROLEprod_candidate=# select usename, useconfig from pg_user; usename | useconfig
----------------+-------------------------------------------- postgres | {"search_path=\"\""} user2 | {"search_path=public, schema1, schema2, schema3"}
user3 | {"search_path=public, schema1, schema2, schema3"}(3 rows)
prod_candidate=# alter user postgres set search_path to 'operator, gameplay, common';
ALTER ROLEprod_candidate=# select usename, useconfig from pg_user; usename | useconfig ----------------+------------------------------------------------
postgres | {"search_path=\"public, schema1, schema2, schema3\""} user2 | {"search_path=public, schema1, schema2, schema3"} user3 | {"search_path=public, schema1, schema2, schema3"}
(3 rows)
Regards,
Colin

Hi Colin,you should rather set the path with:
alter user postgres set search_path = public, schema1, schema2, schema3;

szymon