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

From: Andreas Karlsson <andreas(at)proxel(dot)se>
To: Euler Taveira <euler(at)timbira(dot)com(dot)br>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: pg_restore --convert-to-text
Date: 2019-02-15 01:41:13
Message-ID: df8b99c3-2820-96cb-6669-4ee141ff81e4@proxel.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 14/02/2019 01.31, Euler Taveira wrote:
> Em qua, 13 de fev de 2019 às 19:56, Andrew Gierth
> <andrew(at)tao11(dot)riddles(dot)org(dot)uk> escreveu:
>> I propose we add a new option: --convert-to-text or some such name, and
>> then make pg_restore throw a usage error if neither -d nor the new
>> option is given.
>>
> However, I agree that pg_restore to stdout if -d wasn't specified is
> not a good default. The current behavior is the same as "-f -"
> (however, pg_restore doesn't allow - meaning stdout). Isn't it the
> case to error out if -d or -f wasn't specified? If we go to this road,
> -f option should allow - (stdout) as parameter.

Agreed, "-f -" would be acceptable. I use pg_restore to stdout a lot,
but almost always manually and would have to have to remember and type
"--convert-to-text".

Andreas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2019-02-15 01:46:01 Re: Using POPCNT and other advanced bit manipulation instructions
Previous Message Bruce Momjian 2019-02-15 01:15:38 Re: Early WIP/PoC for inlining CTEs