Bug #953: pg_dump dies on tables with no columns

Ziga Kranjec (ziga(at)ljudmila(dot)org) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
pg_dump dies on tables with no columns

Long Description
version 7.3.2

pg_dump stated dying while dumping some of my databases.
The error message is:

pg_dump: SQL command to dump the contents of table "fields" failed
pg_dump: Error message from server: ERROR: parser: parse error at or near ")" at character 19
pg_dump: The command was: COPY wdbi.fields () TO stdout;

Further investigation shows that there is a problem with
COPY SQL command:

db=# copy wdbi.fields to stdout;
ERROR: MemoryContextAlloc: invalid request size 0
lost synchronization with server, resetting connection

Table wdbi.fields looks like this:

CREATE TABLE fields (
);

that is, no columns, which otherwise seems fine,
as far as Postgres is concerned.

This table was created using a database modelling tool;
so far just a class was created. Columns haven't been
added yet (but they eventually will).

This is a major annoyance, because it stops backups from
working :-(
Actually, pg_dump will dump everything up to the offending
table, so "COPY table FROM stdin" is the last thing it prints...

Sample Code
create table foo ();
copy foo to stdout;

No file was uploaded with this report