Re: BUG #15893: pg_dump is not working like as postgres version 10

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: shaurya jain <12345shaurya(at)gmail(dot)com>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15893: pg_dump is not working like as postgres version 10
Date: 2019-07-19 09:44:51
Message-ID: 20190719094451.GA6984@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jul 19, 2019 at 12:22:36PM +0530, shaurya jain wrote:
> My concern is so simple that the below command is taking full instance
> backup in version 10 and in 11 it is taking only Postgres DB backup.
>
> pg_dump -U postgres -Fc >> all_db_04_07_2019.dump --verbose
>
> Kindly suggest me some way to take full instance back up and restore a
> particular DB.

Please do not top-post. This is not the style of the PostgreSQL
community mailing lists.

I am afraid that you still are giving zero clue about what is going
wrong. Giving a command does not help. Giving information about the
error happening does help, and pg_dump reports any errors when it
normally words, even if you use incorrect credentials to connect to
PostgreSQL. Are you sure for example that your database user is the
correct one? Without this information, nobody will be able to
understand what is wrong and help you. If you do not know how to
capture errors from stderr, well...
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Kellerer 2019-07-19 10:06:50 Re: BUG #15893: pg_dump is not working like as postgres version 10
Previous Message Rick Vincent 2019-07-19 08:20:26 RE: BUG #15908: Xpath operations fail