| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | <liao(at)sandiego(dot)edu>, <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Bug #540: pg_dump a simple table can fail if other |
| Date: | 2001-12-17 01:10:45 |
| Message-ID: | 20011216170658.F45228-100000@megazone23.bigpanda.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, 16 Dec 2001 pgsql-bugs(at)postgresql(dot)org wrote:
> luby liao (liao(at)sandiego(dot)edu) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> pg_dump a simple table can fail if other view/triggers are faulty
>
> Long Description
> We use Postgresql 7.1.2 on a Redhat 7.0 Linux PC. My CS145 students
> all work in a database called cs145. Some students introduced
> unintended faulty views and triggers into the database. When a
> student tried to pg_dump his own tables, he got error messages that
> say that other people's views or triggers were faulty.
We're going to need some additional information for this to be a
complete report. What options were used to pg_dump, how far the dump
got and what messages were reported.
It'd be nice to know what was meant by faulty views and triggers or
an example to reproduce the problem.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-12-17 01:31:35 | Re: Bug #540: pg_dump a simple table can fail if other |
| Previous Message | pgsql-bugs | 2001-12-17 00:05:37 | Bug #540: pg_dump a simple table can fail if other view/triggers are faulty |