Re: pg_dump behaviour changed in 7.1.3?

From: Christian Schröder <cs(at)theta-soft(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dump behaviour changed in 7.1.3?
Date: 2002-01-17 16:27:45
Message-ID: 3C46FB81.B86B2B59@theta-soft.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2002-01-17 16:36:54 Re: how to limit postgresql process and memory time
Previous Message Brent Verner 2002-01-17 16:25:08 Re: how to limit postgresql process and memory time