On 1/30/07, Tom Lane <[EMAIL PROTECTED]> wrote:
"Peter Koczan" <[EMAIL PROTECTED]> writes:
> So, is there any remedy to my problem (see below) short of granting
> superuser access? Is this a bug (which I would then report on the
> appropriate channels)?
It's not a bug.
> As for Tom's suggestio
"Peter Koczan" <[EMAIL PROTECTED]> writes:
> So, is there any remedy to my problem (see below) short of granting
> superuser access? Is this a bug (which I would then report on the
> appropriate channels)?
It's not a bug.
> As for Tom's suggestion, there's no way to specify the database in
> pg_d
I should be a little more specific. The way we currently do backups is that
this backup user dumps user/group data (i.e. the --globals-only flag) for
pg_dumpall, and we pg_dump individual databases.
We grant read access to this backup user for all non-system
tables/views/etc. (and usage for non-s
"Peter Koczan" <[EMAIL PROTECTED]> writes:
> Right now, we run pg_dumpall as a non-superuser,
[ raised eyebrow... ] That's never been a recommended procedure.
> The weird thing is, whenever I run this exact same command from psql as the
> backup user, it works.
Maybe you're not trying it in the
Hi all,
Thanks for your help thus far. I almost have 8.2 ready (hooray no more
ancient 7.4). I do have one more problem which is likely the last thing
before pushing out live support. pg_dumpall isn't working.
Right now, we run pg_dumpall as a non-superuser, let's call it backup, whom
we give re
Hi,
First, i didn't find a resolution to my problem in the archives ...
I use Postgresql 7.4 and I have a big problem dumping databases :
This is the view from the command line (postmaster launched on port 5228
to isolate it from other requests) :
pluton:/etc/init.d # ./postgres start
Starti
