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

From Christian Schröder
Subject Re: pg_dump behaviour changed in 7.1.3?
Date
Msg-id 3C46FB81.B86B2B59@theta-soft.de
Whole thread Raw
In response to pg_dump behaviour changed in 7.1.3?  (Christian Schröder <cs@theta-soft.de>)
List pgsql-general
Tom Lane wrote:

> > 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!
>
> [ thinks ... ]  Are these triggers on plain tables, or views?

Triggers on tables. As I explained they are the triggers which have been
auto-created to check referential integrity.

Regards,

    Christian


pgsql-general by date:

Previous
From: Brent Verner
Date:
Subject: Re: how to limit postgresql process and memory time
Next
From: Tom Lane
Date:
Subject: Re: how to limit postgresql process and memory time