Re: pg_upgrade & tablespaces

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: 2013-12-31 22:08:04
Message-ID: 52C34044.1020906@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

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?

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message peterlen 2013-12-31 22:16:23 Re: Format of Pioint datatype.... lat/long or long/lat??
Previous Message Adrian Klaver 2013-12-31 22:02:59 Re: pg_upgrade & tablespaces

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-12-31 22:14:11 What exactly is drop-index-concurrently-1.spec trying to test?
Previous Message Adrian Klaver 2013-12-31 22:02:59 Re: pg_upgrade & tablespaces