From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | pinker <pinker(at)onet(dot)eu>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump (PostgreSQL) 9.4.1 - delay in checking if file exists |
Date: | 2015-07-07 14:56:30 |
Message-ID: | 559BE89E.1020307@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 07/07/2015 07:12 AM, pinker wrote:
> Adrian Klaver-4 wrote
>> So how did you get the wrong file name then, the pgAdmin backup dialog
>> has a file selector?
>>
>> Or did you cut and paste into the file field?
>
> Anyway, shouldn't postgresql first check if dump can be saved? and then
> start doing it?
Ignore my comment about
'saving database definition'
Looking at the source that is from pg_dump and appears when you run with
--verbose, which I do not do. That explains why I am not seen it.
>
>
>
> --
> View this message in context: http://postgresql.nabble.com/pg-dump-PostgreSQL-9-4-1-delay-in-checking-if-file-exists-tp5856890p5856979.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | pinker | 2015-07-07 15:15:55 | Re: pg_dump (PostgreSQL) 9.4.1 - delay in checking if file exists |
Previous Message | Adrian Klaver | 2015-07-07 14:26:00 | Re: pg_dump (PostgreSQL) 9.4.1 - delay in checking if file exists |