| From: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
|---|---|
| To: | Euler Taveira <euler(dot)taveira(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_restore error message |
| Date: | 2020-05-07 22:17:14 |
| Message-ID: | CAEudQApAWpJscpdfr=D6M6217iTxnuyKFoHK7gKHQMJKYwwVWg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Em qui., 7 de mai. de 2020 às 18:54, Euler Taveira <
euler(dot)taveira(at)2ndquadrant(dot)com> escreveu:
> Hi,
>
> While investigating a pg_restore error, I stumbled upon a message that is
> not so useful.
>
> pg_restore: error: could not close data file: No such file or directory
>
> Which file? File name should be printed too like in the error check for
> cfopen_read a few lines above.
>
Can suggest improvements?
1. free (398 line) must be pg_free(buf)';
2. %m, is a format to parameter, right?
But what parameter? Both fatal call, do not pass this parameter, or is
it implied?
regards,
Ranier Vilela
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2020-05-07 22:54:17 | Re: Incremental sorts and EXEC_FLAG_REWIND |
| Previous Message | Euler Taveira | 2020-05-07 21:54:06 | pg_restore error message |