Re: Upgrade to 9.1 causing function problem - Mailing list pgsql-general

From Willem Buitendyk
Subject Re: Upgrade to 9.1 causing function problem
Date
Msg-id 63372351-D2C4-4FB8-8918-DC92554198F7@pcfish.ca
Whole thread Raw
In response to Re: Upgrade to 9.1 causing function problem  (Adrian Klaver <adrian.klaver@gmail.com>)
Responses Re: Upgrade to 9.1 causing function problem  (Rob Sargent <robjsargent@gmail.com>)
Re: Upgrade to 9.1 causing function problem  (Adrian Klaver <adrian.klaver@gmail.com>)
Re: Upgrade to 9.1 causing function problem  (John R Pierce <pierce@hogranch.com>)
List pgsql-general
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
itclearly does.  I'm at a loss. 

Willem



On 2012-02-23, at 11:41 AM, Adrian Klaver wrote:

> On Thursday, February 23, 2012 11:18:46 am Willem Buitendyk wrote:
>> I have recently upgraded my database from 8.4 to 9.1.  In the process I
>> have moved everything to a different schema.  Postgis is occupying the
>> public schema.  Everything is working fine except for some of my own
>> functions. Here is a small function and table that will not update when I
>> perform the following code:    select _me_set_process_month('2012-01-01');
>>    It will run but the resulting table will not update.  Any ideas?
>
> What does the Postgres log say?
> What is your search_path set to?
> Is there more than one activity_month?
>
> My guess is that your search_path is limiting the visibility of the table.
> Without an explicit schema qualification of the table, Postgres will use the
> search_path to locate a table. The logs should say something or you can change
> the function to point to a schema qualified table name, if you do want to change
> the search_path.
>
> --
> Adrian Klaver
> adrian.klaver@gmail.com


pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Upgrade to 9.1 causing function problem
Next
From: Jayashankar K B
Date:
Subject: Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8