| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "C(dot) R(dot) Oldham" <cro(at)ncacasi(dot)org> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_dump problem |
| Date: | 2001-06-13 16:33:03 |
| Message-ID: | 26934.992449983@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"C. R. Oldham" <cro(at)ncacasi(dot)org> writes:
> p0 rack[46]% pg_dump -S postgres --no-owner test > ~/test.dump
> dumpSequence(user_id_sequence): SELECT failed. Explanation from backend:
> 'ERROR: user_id_sequence: Permission denied.
Hmm. Which user is pg_dump connecting as? (The -S switch does not
answer this question, btw; that only determines what's emitted into
the output script.) I would expect behavior like this if you are
connecting as someone who's neither a superuser nor the sequence
owner. Check PGUSER and USER environment variables.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-06-13 16:35:13 | Re: Multiple pq_flush: send() failed: Broken pipe |
| Previous Message | Bruce Momjian | 2001-06-13 16:25:17 | Re: 7.1.2 temporary file area |