pg_dump: Too much in COPY ouput - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject pg_dump: Too much in COPY ouput
Date
Msg-id 200106011256.f51CuoV82845@hub.org
Whole thread Raw
Responses Re: pg_dump: Too much in COPY ouput  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Jean-Francois Leveque (leveque@webmails.com) reports a bug with a severity of 4
The lower the number the more severe it is.

Short Description
pg_dump: Too much <SPACE> in COPY ouput

Long Description
System: SuSE 7.0
select version(); :
PostgreSQL 7.1.2 on i686-pc-linux-gnu, compiled by GCC 2.95.2

pg_dump inserts an extra <SPACE> between double-quoted tablename
and FROM.

This was not the case with the version I used before:

System: SuSE 7.0
PostgreSQL RPM: postgres-7.0.2-29
select version(); :
PostgreSQL 7.0.2 on i686-pc-linux-gnu, compiled by gcc 2.95.2

Example form two pg_dump outputs
7.1.2 :
    COPY "list"  FROM stdin;
7.0.2 :
    COPY "list" FROM stdin;


Sample Code


No file was uploaded with this report

pgsql-bugs by date:

Previous
From: pgsql-bugs@postgresql.org
Date:
Subject: GRANT SELECT ON ... TO username does REVOKE ALL ON ... FROM PUBLIC at the same time
Next
From: Tom Lane
Date:
Subject: Re: pg_dump: Too much in COPY ouput