Re: pg_restore: implied data-only restore\n

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Cc: Andreas Laggner <andreas(dot)laggner(at)vti(dot)bund(dot)de>
Subject: Re: pg_restore: implied data-only restore\n
Date: 2011-02-04 15:37:03
Message-ID: 201102040737.04417.adrian.klaver@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Friday, February 04, 2011 4:35:22 am Andreas Laggner wrote:
> Hi list,
>
> i did a dump (one table)
> pg_dump -t tempo.lucas_p1000 -Fc -o -h 134.110.37.20 -p 5432 -U andi -W
> gis > /disk2/samba/exportdb/postgres/lucas_p1000_test.out
>
> and when a want to restore the table
> pg_restore -d gis -t tempo.lucas_p1000 -Fc -v -h 134.110.37.20 -p 5432
> -U andi -W /disk2/samba/exportdb/postgres/lucas_p1000_test.out
>
> pg_restore shows this error:
> pg_restore: implied data-only restore\n
>
> what is wrong?

Did it restore the data?

According to the source pg_backup_archiver.c:

"Work out if we have an implied data-only restore. This can happen if
the dump was data only or if the user has used a toc list to exclude
all of the schema data. All we do is look for schema entries - if none
are found then we set the dataOnly flag."

Are you sure you are picking up the right lucas_p100_test.out file? Maybe there
is a data only version lying around. One way to test is have pg_restore restore
to a file instead of database:

pg_restore -f tempo.sql -t tempo.lucas_p1000
/disk2/samba/exportdb/postgres/lucas_p1000_test.out

>
> thanks for help Andreas

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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bob Price 2011-02-04 16:08:18 Re: how to avoid repeating expensive computation in select
Previous Message Andreas Laggner 2011-02-04 12:35:22 pg_restore: implied data-only restore\n