| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] pg_dump not in very good shape |
| Date: | 2000-01-16 20:12:20 |
| Message-ID: | Pine.LNX.4.21.0001161848440.1636-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2000-01-15, Tom Lane mentioned:
> I have repaired the most recently introduced coredump in pg_dump,
> but it still crashes on the regression test database.
Which brings up the idea why the regression tests don't test pg_dump. It's
just as important to people as the backend. psql already gets tested more
or less. Would it not be a decent idea to do a
pg_dump regress > out
diff out expected.out
at the end of the tests? That way we could catch these problems
earlier. (Especially since I'm not sure how many people use pg_dump at all
during development.)
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-01-16 20:13:03 | Re: [HACKERS] flex |
| Previous Message | Peter Eisentraut | 2000-01-16 20:12:01 | Re: [HACKERS] pg_dump not in very good shape |