Re: [HACKERS] pg_dump not in very good shape

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: [HACKERS] pg_dump not in very good shape
Дата
Msg-id 200001170619.BAA13413@candle.pha.pa.us
обсуждение исходный текст
Ответ на Re: [HACKERS] pg_dump not in very good shape  (Peter Eisentraut <peter_e@gmx.net>)
Ответы Re: [HACKERS] pg_dump not in very good shape  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
> 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.)

Actually the megatest is:
pg_dump regress > outdropdb regressioncreatedb regressionpsql regression < outpg_dump regress > out2diff out out2

That is the pg_dump test, and someone usually does it as part of
regression testing before each release.

It would be nice to add this to test/regress/Makefile maybe.

--  Bruce Momjian                        |  http://www.op.net/~candle pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: [HACKERS] RE: Getting rid of setheapoverride (was Re: [COMMITTERS] heap.c)
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: [HACKERS] Temp Table Memory Leak