Re: Problems with pg_dump
От | papapep |
---|---|
Тема | Re: Problems with pg_dump |
Дата | |
Msg-id | 3DFE292E.2090001@gmx.net обсуждение исходный текст |
Ответ на | Re: Problems with pg_dump (<ghaverla@freenet.edmonton.ab.ca>) |
Ответы |
Re: Problems with pg_dump
|
Список | pgsql-novice |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > You mean you're doing > pg_dump ... >DATABASE.out Right > 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. No wonder > it's failing. Read-only status wouldn't be much protection if it didn't > fail, no? Of course.. :-D 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. Josep Sànchez [papapep] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) - WinPT 0.5.13 iD8DBQE9/ikM2vx52x0kyz4RAo8cAJ9cBmHQsl14z6JthjmwJmLTowCMZACcD37R 0i9O67tnCyDQEpO0FbAJN8k= =fJhR -----END PGP SIGNATURE-----
В списке pgsql-novice по дате отправления: