From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: 唯一★ <270246512@qq.com>
Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: 回复: 回复: BUG #16101: tables in the DB is not available after pg_restore
Date: Wed, 13 Nov 2019 16:18:03 +0100
Message-ID: <20191113151803.6ye47vh3vyp5ufah@development> (raw)
In-Reply-To: <tencent_9DD805D110A0A91F987ADEAB25EE2D69BB05@qq.com>
References: <16101-5a569e5aac6aa84e@postgresql.org>
<20191108111339.xlopjkbwfhxfvwt3@development>
<tencent_5865E10D689BCC05DFD0BC291ED869BEAA05@qq.com>
<20191113133029.kagiy6vjjeoguatp@development>
<tencent_9DD805D110A0A91F987ADEAB25EE2D69BB05@qq.com>
On Wed, Nov 13, 2019 at 10:43:20PM +0800, 唯一★ wrote:
>hi,
>
>
>The restore command is "pg_dump -h 127.0.0.1 -U postgres -d cmdb -p 5432 -Fc -f bk_1"
>Here are reproduce steps.
>1. login in the postgres DB with super user postgres and create DB
> CREATE DATABASE cmdb OWNER cm WITH TEMPLATE = template0;
> GRANT ALL PRIVILEGES ON DATABASE cmdb to cm;
>
>
>
>2.pop the data to DB.
> pgbench -i -h 127.0.01 -U cm -s 20 -d cmdb
>
>
>3.use the pg_dump to backup the data.
> pg_dump -h 127.0.0.1 -U postgres -d cmdb -p 5432 -Fc -f bk_1
>4.take the restore via pg_restore.
> pg_restore -h 127.0.0.1 -U postgres -d cmdb bk_1 -c -v
>
Works just fine for me:
[user@development ~]$ pg_ctl -D tmp/data init
...
[user@development ~]$ pg_ctl -D tmp/data -l pg.log start
waiting for server to start.... done
server started
[user@development ~]$ createdb cmdb
[user@development ~]$ pgbench -i -s 1 cmdb
dropping old tables...
NOTICE: table "pgbench_accounts" does not exist, skipping
NOTICE: table "pgbench_branches" does not exist, skipping
NOTICE: table "pgbench_history" does not exist, skipping
NOTICE: table "pgbench_tellers" does not exist, skipping
creating tables...
generating data...
100000 of 100000 tuples (100%) done (elapsed 0.06 s, remaining 0.00 s)
vacuuming...
creating primary keys...
done.
[user@development ~]$ pg_dump -d cmdb -p 5432 -Fc -f bk_1
[user@development ~]$ pg_restore -d cmdb2 bk_1 -c -v
pg_restore: connecting to database for restore
...
pg_restore: warning: errors ignored on restore: 7
[user@development ~]$ psql cmdb2
psql (12.1)
Type "help" for help.
cmdb2=# \d
List of relations
Schema | Name | Type | Owner
--------+------------------+-------+-------
public | pgbench_accounts | table | user
public | pgbench_branches | table | user
public | pgbench_history | table | user
public | pgbench_tellers | table | user
(4 rows)
Are you sure you're running the pg_restore on the right machine and not
on the same system where you did the pg_dump? Don't you have some
per-user search_path setting applied using ALTER USER?
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: tomas.vondra@2ndquadrant.com, 270246512@qq.com
Subject: Re: 回复: 回复: BUG #16101: tables in the DB is not available after pg_restore
In-Reply-To: <20191113151803.6ye47vh3vyp5ufah@development>
References: <16101-5a569e5aac6aa84e@postgresql.org> <20191108111339.xlopjkbwfhxfvwt3@development> <tencent_5865E10D689BCC05DFD0BC291ED869BEAA05@qq.com> <20191113133029.kagiy6vjjeoguatp@development> <tencent_9DD805D110A0A91F987ADEAB25EE2D69BB05@qq.com> <20191113151803.6ye47vh3vyp5ufah@development>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox