| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Andre Lucas <andre(at)amazoniasistemas(dot)com(dot)br>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: PSQL Help |
| Date: | 2020-02-18 03:39:16 |
| Message-ID: | 32736.1581997156@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Monday, February 17, 2020, Andre Lucas <andre(at)amazoniasistemas(dot)com(dot)br>
> wrote:
>> psql -h localhost -U postgres NovoBD -f Backup17.sql
>> “psql: warning: extra command-line argument "-f" ignored
>> psql: warning: extra command-line argument "Backup17.sql" ignored
> You command doesn’t match the documented syntax:
> psql [option...] [dbname [username]]
> Hint: NovoBD is the “dbname”
FWIW, Andres' example *will* work on some platforms, because glibc's
getopt_long() takes it upon itself to rearrange the arguments.
But it doesn't work everywhere, which is why we only document/recommend
the stricter argument order.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hazuki Amamiya | 2020-02-18 03:48:49 | Re: Possible memory leak in PostgreSQL 12.2 on truncate, insert or delete when type interval is involved |
| Previous Message | David G. Johnston | 2020-02-18 03:06:13 | Re: PSQL Help |