pg_dump behaviour changed in 7.1.3? - Mailing list pgsql-general

From Christian Schröder
Subject pg_dump behaviour changed in 7.1.3?
Date
Msg-id 3C462961.2B6B6370@theta-soft.de
Whole thread Raw
Responses Re: pg_dump behaviour changed in 7.1.3?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hi!

I'm not sure if this message reached you because I received an error
notification. I will simply post it again ...
I've encountered a problem during use of pg_dump: The database contains
several tables and some referential integrities between them, i.e. some
triggers. We use a pg_dump to backup the database to a file. Now I
noticed that the dump doesn't contain the triggers! I tried to find out
what the problem is and have come to this solution: The backup is done
by a user that doesn't own the tables. He has read and write permission
to the tables, but that does no longer seem to be enough. But I don't
know what permissions are necessary to perform the dump. And I don't
know how to set permission for triggers -- they are not even listed when
I type "\d"!
The problem is new since we updated from server version 7.1.2 to 7.1.3.
In 7.1.2 the dump was complete (including the triggers) and in 7.1.3 it
is not.
Hope you can help me with this!

Regards

    Christian

pgsql-general by date:

Previous
From: Rob Brown-Bayliss
Date:
Subject: external input for primary key
Next
From: Stephan Szabo
Date:
Subject: Re: VARCHAR to INTEGER conversion