From: | Jan Wieck <wieck(at)debis(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] pg_dump not in very good shape |
Date: | 2000-01-17 15:06:04 |
Message-ID: | 38832FDC.5B5EC18D@debis.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Actually the megatest is:
>
> > pg_dump regress > out
> > dropdb regression
> > createdb regression
> > psql regression < out
> > pg_dump regress > out2
> > diff 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.
>
> That's a good thought --- it eliminates both the platform-specific
> issues and the problem of adding a bulky reference file to the
> distribution.
Still an incomplete test at all.
It doesn't guarantee, that the resulting dump is what you
really need to restore the database. For example, I'm not
sure that FOREIGN KEY constraints are actually dumped
correct (as constraint trigger statements after the data
load). So it might work, and result in the same, wrong dump
again.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-01-17 15:58:15 | Re: [HACKERS] Foreign keys: unexpected result from ALTER TABLE... ADD CONSTRAINT... |
Previous Message | Theo Kramer | 2000-01-17 15:03:30 | Re: [HACKERS] DefineQueryRewrite: rule plan string too big. |