| From: | Joseph Kregloh <jkregloh(at)sproutloud(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, John R Pierce <pierce(at)hogranch(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade & tablespaces |
| Date: | 2014-01-01 00:03:15 |
| Message-ID: | CAAW2xfdxxomJ=kuz=RiOwg-dtqMEVXwjYh685eF4S=7+zbzHxg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Tue, Dec 31, 2013 at 5:08 PM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>wrote:
> On 12/31/2013 01:31 PM, Joseph Kregloh wrote:
>
>>
>> ERROR: relation "sys_errors" does not exist
>> LINE 1: SELECT * FROM sys_errors ORDER BY created_ts DESC LIMIT
>> 100;
>> ^
>> ********** Error **********
>>
>> ERROR: relation "sys_errors" does not exist
>> SQL state: 42P01
>> Character: 15
>>
>>
>> sys_errors is a table in the tablespace correct?
>>
>>
>> Yes it is.
>>
>
> Completely different thought, is sys_errors in a schema other than PUBLIC?
>
> If so, what is your search_path setting for the new server?
>
>
I set the search_path to the same value that the 9.0 instance had and that
seemed to do the trick. I will know more on Thursday when I get some time
to play with it.
Thanks,
Happy New Year.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2014-01-01 00:06:54 | Re: pg_upgrade & tablespaces |
| Previous Message | Adrian Klaver | 2013-12-31 23:48:06 | Re: Format of Pioint datatype.... lat/long or long/lat?? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2014-01-01 00:06:54 | Re: pg_upgrade & tablespaces |
| Previous Message | Pavel Stehule | 2013-12-31 22:46:05 | Re: proposal: persistent plpgsql plugin info - field plugin_info for plpgsql_function structure |