Re: [HACKERS] pg_dump not in very good shape - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] pg_dump not in very good shape
Date
Msg-id Pine.LNX.4.21.0001161848440.1636-100000@localhost.localdomain
Whole thread Raw
In response to pg_dump not in very good shape  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] pg_dump not in very good shape
Re: [HACKERS] pg_dump not in very good shape
List 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@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] RE: Getting rid of setheapoverride (was Re: [COMMITTERS] heap.c)
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Temp Table Memory Leak