Re: pgsql: Un-break pg_dump for the case of zero-column tables. - Mailing list pgsql-committers

From Magnus Hagander
Subject Re: pgsql: Un-break pg_dump for the case of zero-column tables.
Date
Msg-id 9837222c1002232311t22a1349fq7d6ceb892a57716@mail.gmail.com
Whole thread Raw
In response to pgsql: Un-break pg_dump for the case of zero-column tables.  (tgl@postgresql.org (Tom Lane))
List pgsql-committers
2010/2/24 Tom Lane <tgl@postgresql.org>:
> Log Message:
> -----------
> Un-break pg_dump for the case of zero-column tables.
>
> This was evidently broken by the CREATE TABLE OF TYPE patch.  It would have
> been noticed if anyone had bothered to try dumping and restoring the
> regression database ...

Is there a point in doing that at the end of "make check"? Or as a
separate step on the buildfarm?

It would at least find problems that cause syntax errors or such
things when loading, even if we don't compare the full data?

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

pgsql-committers by date:

Previous
From: itagaki@postgresql.org (Takahiro Itagaki)
Date:
Subject: pgsql: Remove useless codes to initialize TupleDesc from dblink_exec.
Next
From: Stefan Kaltenbrunner
Date:
Subject: Re: pgsql: Remove pre-7.4 documentaiton mentions, now that 8.0 is the oldest