Skip site navigation (1) Skip section navigation (2)

Re: Problems with pg_dump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: papapep <papapep(at)gmx(dot)net>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Problems with pg_dump
Date: 2002-12-16 21:19:22
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-novice
papapep <papapep(at)gmx(dot)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 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

In response to


pgsql-novice by date

Next:From: Daniel WhelanDate: 2002-12-16 21:24:13
Subject: Batch Table Creation - Foreign Key Problem
Previous:From: ghaverlaDate: 2002-12-16 20:01:01
Subject: Re: Problems with pg_dump

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group