Re: Upgrade to 9.1 causing function problem

From: Willem Buitendyk <willem(at)pcfish(dot)ca>
To: Rob Sargent <robjsargent(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Upgrade to 9.1 causing function problem
Date: 2012-02-23 20:28:33
Message-ID: A9D0B006-DE92-4EAC-84D6-B26E5233FB0F@pcfish.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

crabby=# \dv
List of relations
Schema | Name | Type | Owner
----------+-------------------------------------------+------+----------
crabdata | Total XXX XXXXX by XXX | view | postgres

also;

crabby=# show search_path;
search_path
-------------
crabdata
(1 row)

On 2012-02-23, at 12:16 PM, Rob Sargent wrote:

> On 02/23/2012 12:49 PM, 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.
>>
>> 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(dot)klaver(at)gmail(dot)com
>>
> Who owes/owned "crabdata" schema?
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2012-02-23 20:57:33 Re: Upgrade to 9.1 causing function problem
Previous Message Tom Lane 2012-02-23 20:19:45 Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8