On 03/05/10 01:30, Tom Lane wrote:
> Russell Smith writes:
>
>> On 02/05/10 01:36, Tom Lane wrote:
>>
>>> No, that's the intended place for them given the current division of
>>> labor between pg_dump and pg_dumpall. There have been complaints before
>>> about this, but no one has propose
Russell Smith writes:
> On 02/05/10 01:36, Tom Lane wrote:
>> No, that's the intended place for them given the current division of
>> labor between pg_dump and pg_dumpall. There have been complaints before
>> about this, but no one has proposed a better approach (where better
>> means "fixes this
On 02/05/10 01:36, Tom Lane wrote:
> Russell Smith writes:
>
>> Is this considered a bug that the only way to do a dump/restore with
>> database privileges is to use pg_dumpall?
>>
> No, that's the intended place for them given the current division of
> labor between pg_dump and pg_dumpall
Russell Smith writes:
> Is this considered a bug that the only way to do a dump/restore with
> database privileges is to use pg_dumpall?
No, that's the intended place for them given the current division of
labor between pg_dump and pg_dumpall. There have been complaints before
about this, but no
Hi,
I've recently upgraded to PostgreSQL 8.4 as Redhat had begun supporting
it. I have tried to dump database grants, but have only found an
obscure way to do it.
I would expect;
postgres$ pg_dump -Fc database_name > backup.pgdump
would include all of the GRANT CONNECT on database_name TO "Rol
