On 07/09/2015 01:24 AM, pinker wrote:
Tom Lane-2 wrote
$ time pg_dump -f /z/q regression
pg_dump: [archiver] could not open output file "/z/q": No such file or
directory
real0m1.164s
user0m0.062s
sys 0m0.034s
However, I don't see that with any of the non-plain-text output formats:
Tom Lane-2 wrote
> $ time pg_dump -f /z/q regression
> pg_dump: [archiver] could not open output file "/z/q": No such file or
> directory
>
> real0m1.164s
> user0m0.062s
> sys 0m0.034s
>
> However, I don't see that with any of the non-plain-text output formats:
In my case this is:
p
Adrian Klaver-4 wrote
> That is sort of dangerous:) As an example, do you really want --inserts
> or --column-inserts, they really slow down a restore.
I know, but this time I need it more for versioning/demo version
prepariation so performence isn't important at all, what I care about is
only dd
On 07/07/2015 08:15 AM, pinker wrote:
Adrian Klaver-4 wrote
I was talking about when you ran the backup from pgAdmin. The backup
dialog has a file selector button to select the path/file you want to
back up to. So I was wondering how you got an incorrect path in the
first place? Then it occurre
Adrian Klaver-4 wrote
> I was talking about when you ran the backup from pgAdmin. The backup
> dialog has a file selector button to select the path/file you want to
> back up to. So I was wondering how you got an incorrect path in the
> first place? Then it occurred to me you might not have hav
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?
Ignor
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?
pgAdm
On 07/07/2015 06:55 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?
I've cut, pasted and changed parameters.
I was talking about when you ran the backup from pgA
John McKown writes:
> On Tue, Jul 7, 2015 at 4:26 AM, pinker wrote:
>> I made mistake in a filename in pg_dump command, i.e. have used path from
>> another server, which not exists on this one. pg_dump instead of checking
>> permissions / existence of output file first dumped the whole database a
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?
--
View this message in context:
htt
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?
I've cut, pasted and changed parameters.
--
View this message in context:
http://postgresql.nabble.com/pg-dump-PostgreSQL-
On 07/07/2015 06:00 AM, pinker wrote:
Adrian Klaver-4 wrote
So this was not the actual command you ran as I see no path specification.
Some notes:
1) plain format is the default so it does not need to specified.
2) Either --inserts or --column-inserts not both. FYI this really slows
down the
Adrian Klaver-4 wrote
> So this was not the actual command you ran as I see no path specification.
>
> Some notes:
>
> 1) plain format is the default so it does not need to specified.
>
> 2) Either --inserts or --column-inserts not both. FYI this really slows
> down the restore process.
>
> 3)
On 07/07/2015 05:23 AM, pinker wrote:
John McKown wrote
What version of PostgreSQL? What OS? What was the command line?
*OS*: Linux OptiPlex-760 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Linux Mint 15 Olivia
*pg_dump*: pg_dump (PostgreSQL) 9.
John McKown wrote
> What version of PostgreSQL? What OS? What was the command line?
*OS*: Linux OptiPlex-760 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Linux Mint 15 Olivia
*pg_dump*: pg_dump (PostgreSQL) 9.4.1
*command line:*
opt/PostgreSQL/9.4/
On Tue, Jul 7, 2015 at 4:26 AM, pinker wrote:
> I made mistake in a filename in pg_dump command, i.e. have used path from
> another server, which not exists on this one. pg_dump instead of checking
> permissions / existence of output file first dumped the whole database and
> at the end (after so
I made mistake in a filename in pg_dump command, i.e. have used path from
another server, which not exists on this one. pg_dump instead of checking
permissions / existence of output file first dumped the whole database and
at the end (after some time ... ) threw an error:
(...)
pg_dump: saving dat
17 matches
Mail list logo