Re: pg_dump/pg_restore issues

From: bricklen <bricklen(at)gmail(dot)com>
To: Leonardo M(dot) Ramé <l(dot)rame(at)griensu(dot)com>
Cc: PostgreSql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_dump/pg_restore issues
Date: 2014-02-19 18:08:19
Message-ID: CAGrpgQ8jozx=k-Y=kOdFNNikMw8RaQ6Fc45UpP25Ci3zevsvDA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Feb 19, 2014 at 9:57 AM, Leonardo M. Ramé <l(dot)rame(at)griensu(dot)com>wrote:

> Hi, I'm backing up a big database using the --exclude-table option for
> two tables, say table1 and table2. Then another backup of only those
> tables, so, the final result are three backup files.
>
> basic.backup
> table1.backup
> table2.backup
>
> The problem I'm facing is at the restore moment is that basic.backup
> contains view definitions related to table1 or table2, hence, the
> restore does not create those views.
>
> How do you recommend to workaround this?.
>
> P.S.: I create three files because table1 and table2 are tables with
> blob data, and we use basic.backup to create testing database where we
> don't need blob data.
>

The --section option of pg_dump might allow you dump the views separately.
Alternatively, if you know the names of the views that will fail, you could
pg_dump as you are doing now, but in custom format (-Fc), then use
pg_restore to create a list file from the contents, comment out the views,
pg_restore using the list file (minus those views), then pg_dump using
another list file with *only* those views.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Leonardo M. Ramé 2014-02-19 18:21:53 Re: pg_dump/pg_restore issues
Previous Message Jeff Janes 2014-02-19 17:59:20 Re: How do I track down a possible locking problem?