Re: Upgrade to 9.1 causing function problem

I have it set in postgresql.conf and I've also used:

alter user postgres set search_path = crabdata,public;

looking at the logs after issuing the above alter user command I get:

2012-02-23 13:03:09 PST WARNING invalid value for parameter "search_path": "crabdata, public"
2012-02-23 13:03:09 PST DETAIL schema "crabdata" does not exist

If i look in the schemata table in the catalogs I see crabdata schema is there:

"crabby";"pg_toast";"postgres";"";"";"";""
"crabby";"pg_temp_1";"postgres";"";"";"";""
"crabby";"pg_toast_temp_1";"postgres";"";"";"";""
"crabby";"pg_catalog";"postgres";"";"";"";""
"crabby";"public";"postgres";"";"";"";""
"crabby";"information_schema";"postgres";"";"";"";""
"crabby";"crabdata";"postgres";"";"";"";""

I should note this is on Windows 7 64 bit - using the 32 bit installation of postgresql 9.1

On 2012-02-23, at 12:57 PM, Adrian Klaver wrote:

> On 02/23/2012 11:49 AM, Willem Buitendyk wrote:
>> Here are the log returns:
>>
>> 2012-02-23 11:31:44 PST WARNING invalid value for parameter "search_path": "crabdata"
>> 2012-02-23 11:31:44 PST DETAIL schema "crabdata" does not exist
>>
>> Bizarre because I did set my search path to the schema crabdata but now it is saying that crabdata doesn't exist. But it clearly does. I'm at a loss.
>
> Where did you set the search_path, in postgressql.conf of from a SET command?
>
>>
>> Willem
>>
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)gmail(dot)com