papapep <papapep@gmx.net> writes:
>>> You mean you're doing
>>> pg_dump ... >DATABASE.out
>>> where DATABASE.out already exists and is marked read-only?
> No. It exists after doing pg_dump....etc,etc.. Before I've removed it
> to avoid these problems.
That's odd.
> But the question is, how is that pg_dump creates a file with
> read-only permissions?....astonishing for me....is it the default
> profile?? It isn't written in any of the docs I've read about it.
Well, pg_dump is not creating the file in this situation --- your shell
is. So it's got to have something to do with shell settings. May I
inquire what you have "umask" set to? Also, just exactly what
permissions is the file created with (ls -l output would be good).
regards, tom lane
