From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | Joseph Kregloh <jkregloh(at)sproutloud(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:06:54 |
Message-ID: | 52C35C1E.3080702@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On 12/31/2013 04:03 PM, Joseph Kregloh wrote:
>
>
>
> On Tue, Dec 31, 2013 at 5:08 PM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com
> <mailto: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.
Seems I got tunnel vision on the tablespace issue and overlooked the
simpler explanation initially. Good luck.
>
> Thanks,
> Happy New Year.
>
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Janek Sendrowski | 2014-01-01 00:55:21 | Re: cast hex to int in plpgsql |
Previous Message | Joseph Kregloh | 2014-01-01 00:03:15 | Re: pg_upgrade & tablespaces |
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Karlsson | 2014-01-01 03:14:37 | Re: PoC: Partial sort |
Previous Message | Joseph Kregloh | 2014-01-01 00:03:15 | Re: pg_upgrade & tablespaces |