Re: proposal: pg_restore --convert-to-text

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: "Daniel Verite" <daniel(at)manitou-mail(dot)org>
Cc: José Arthur Benetasso Villanova <jose(dot)arthur(at)gmail(dot)com>, "Imai\, Yoshikazu" <imai(dot)yoshikazu(at)jp(dot)fujitsu(dot)com>, "Euler Taveira" <euler(at)timbira(dot)com(dot)br>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Andreas Karlsson" <andreas(at)proxel(dot)se>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: pg_restore --convert-to-text
Date: 2019-06-12 16:49:14
Message-ID: 87ef3y69b6.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>>>> "Daniel" == Daniel Verite <daniel(at)manitou-mail(dot)org> writes:

Daniel> While testing pg_restore on v12, I'm stumbling on this too.
Daniel> pg_restore without argument fails like that:

Daniel> $ pg_restore
Daniel> pg_restore: error: one of -d/--dbname and -f/--file must be specified

Yeah, that's not good.

How about:

pg_restore: error: no destination specified for restore
pg_restore: error: use -d/--dbname to restore into a database, or -f/--file to output SQL text

--
Andrew (irc:RhodiumToad)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Finnerty 2019-06-12 16:52:09 Re: Adaptive query optimization
Previous Message Alvaro Herrera 2019-06-12 16:46:49 Re: upgrades in row-level locks can deadlock