Re: Upgrade to 9.1 causing function problem

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Cc: Willem Buitendyk <willem(at)pcfish(dot)ca>
Subject: Re: Upgrade to 9.1 causing function problem
Date: 2012-02-23 19:41:59
Message-ID: 201202231142.00059.adrian.klaver@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Willem Buitendyk 2012-02-23 19:49:31 Re: Upgrade to 9.1 causing function problem
Previous Message Willem Buitendyk 2012-02-23 19:18:46 Upgrade to 9.1 causing function problem