Skip site navigation (1) Skip section navigation (2)

Re: pg_dump - 8.3 - schemas

From: "Edward W(dot) Rouse" <erouse(at)comsquared(dot)com>
To: "'Adrian Klaver'" <adrian(dot)klaver(at)gmail(dot)com>
Cc: <pgsql-sql(at)postgresql(dot)org>
Subject: Re: pg_dump - 8.3 - schemas
Date: 2012-02-16 20:17:48
Message-ID: 06ce01ccece8$0cf851b0$26e8f510$@com (view raw or flat)
Thread:
Lists: pgsql-sql
Well, when I do a restore using the created file, reports isn't there. i.e.
the select from reports.table gives an error and, from psql, \l doesn't list
it and \dn doesn't show it. But that all does work on the original database.

> -----Original Message-----
> From: pgsql-sql-owner(at)postgresql(dot)org [mailto:pgsql-sql-
> owner(at)postgresql(dot)org] On Behalf Of Adrian Klaver
> Sent: Thursday, February 16, 2012 2:39 PM
> To: Edward W. Rouse
> Cc: pgsql-sql(at)postgresql(dot)org
> Subject: Re: [SQL] pg_dump - 8.3 - schemas
> 
> On 02/16/2012 11:31 AM, Edward W. Rouse wrote:
> > To answer the second question first, yes; both as the same user.
> >
> > pg_dump -v -f $bkfile -F c -U $USER $DATABASE
> 
> 
> So how are you determining that only the public schema is being dumped?
> One thing to check is the search_path setting in postgresql.conf. This
> can create the illusion that only one schema is available in a
> database.
> One way to check is to use the fully qualified name for a table you
> know
> to be in the reports schema. Ex:
> 
> select * from reports.some_table;
> 
> >
> >
> >
> >
> --
> Adrian Klaver
> adrian(dot)klaver(at)gmail(dot)com
> 
> --
> Sent via pgsql-sql mailing list (pgsql-sql(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-sql


In response to

Responses

pgsql-sql by date

Next:From: Adrian KlaverDate: 2012-02-16 20:22:06
Subject: Re: pg_dump - 8.3 - schemas
Previous:From: Adrian KlaverDate: 2012-02-16 19:38:49
Subject: Re: pg_dump - 8.3 - schemas

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group