Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-24 Thread Adrian Klaver
On Friday, February 24, 2012 10:31:44 am Willem Buitendyk wrote: > Ok I must be doing something wrong. I tried the same test on my old server > running 8.3 which has had no problem with anything up till now (but also > only working within public schema). So I am obviously not working with > schem

Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-24 Thread Willem Buitendyk
I tried as you suggested and my results are: crabby=# SELECT length(schema_name), schema_name from information_schema.schemat a; length |schema_name + 8 | pg_toast 9 | pg_temp_1 15 | pg_toast_temp_1 10 | pg_catalog 6 | public 18 | i

Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-24 Thread Willem Buitendyk
Ok I must be doing something wrong. I tried the same test on my old server running 8.3 which has had no problem with anything up till now (but also only working within public schema). So I am obviously not working with schemas correctly. Will read the manual for hopefully a deeper understandi

Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-24 Thread Willem Buitendyk
I did create the schemas with PgAdmin. As a test I also created another schema in psql and it too has the same problems with the function not working. I also created the function this time without relying on search_path and even altered the function and tables names slightly just in case there

Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-23 Thread Adrian Klaver
On Thursday, February 23, 2012 1:53:42 pm Willem Buitendyk wrote: > Both via psql and PgAdmin. > > Yes only one database cluster. > Another thought. Did you CREATE the schema using PgAdmin and if so, might you have inadvertently put in a trailing or leading space ? I ask because if I remember

Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-23 Thread Adrian Klaver
On 02/23/2012 01:53 PM, Willem Buitendyk wrote: Both via psql and PgAdmin. Yes only one database cluster. 1) Did you try Johns recommendation, just to be sure?: " add the database name to your log_line_prefix ... I use something like... log_line_prefix = '%m %u@%d[%p]: ' " 2) So what ha

Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-23 Thread Willem Buitendyk
Both via psql and PgAdmin. Yes only one database cluster. On 2012-02-23, at 1:32 PM, Adrian Klaver wrote: > On 02/23/2012 01:08 PM, Willem Buitendyk wrote: >> I have it set in postgresql.conf and I've also used: >> >> alter user postgres set search_path = crabdata,public; >> >> looking at t

Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-23 Thread Adrian Klaver
On 02/23/2012 01:08 PM, Willem Buitendyk wrote: 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_

Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-23 Thread Adrian Klaver
On 02/23/2012 01:15 PM, Igor Polishchuk wrote: Actually, what works is set search_path='crabdata', 'public' ; Yea, I was not clear here. I was referring to postgresql.conf setting. -- Adrian Klaver adrian.kla...@gmail.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql

Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-23 Thread Igor Polishchuk
Actually, what works is set search_path='crabdata', 'public' ; On 2/23/12 1:10 PM, "Adrian Klaver" wrote: > On 02/23/2012 01:08 PM, Willem Buitendyk wrote: >> I have it set in postgresql.conf and I've also used: >> alter user postgres set search_path = crabdata,public; >> > > Well search_pat

Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-23 Thread Adrian Klaver
On 02/23/2012 01:08 PM, Willem Buitendyk wrote: I have it set in postgresql.conf and I've also used: alter user postgres set search_path = crabdata,public; Well search_path is a string, so have you tried?; search_path='crabdata,public' -- Adrian Klaver adrian.kla...@gmail.com -- Sent via p

Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-23 Thread John R Pierce
On 02/23/12 11:49 AM, Willem Buitendyk wrote: 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

Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-23 Thread Willem Buitendyk
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

Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-23 Thread Adrian Klaver
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 c

Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-23 Thread Willem Buitendyk
crabby=# \dv List of relations Schema | Name| Type | Owner --+---+--+-- crabdata | Total XXX X by XXX | view | postgres also; crabby=# show sear

Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-23 Thread Rob Sargent
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 c

Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-23 Thread Willem Buitendyk
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

Re: [GENERAL] Upgrade to 9.1 causing function problem

2012-02-23 Thread Adrian Klaver
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. H