From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | hans(at)matfyz(dot)cz |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #12730: pg_dump produces trailing spaces |
Date: | 2015-04-28 23:40:18 |
Message-ID: | 20150428234018.GE31727@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Feb 2, 2015 at 02:31:16PM +0000, hans(at)matfyz(dot)cz wrote:
> The following bug has been logged on the website:
>
> Bug reference: 12730
> Logged by: Hans Ginzel
> Email address: hans(at)matfyz(dot)cz
> PostgreSQL version: 9.4.0
> Operating system: Centos 6.5
> Description:
>
> Hello!
>
> Try
> pg_dump --format=p --schema=information_schema --schema-only --file=is.sql
>
> It seams there are trailing spaces in the comment line
> -- Name: sql_implementation_info; Type: TABLE; Schema: information_schema;
> Owner: postgres; Tablespace:
>
> Skip the string '; Tablespace: ' please, if there is no tablespace or put
> '-' for the tablespace name in the same way as dash is used for Owner when
> the option --no-owner is used.
I looked into this issue and found that the pg_dump code doesn't handle
cases where the reltablespace == 0 (default). I have modified pg_dump
to test for a zero-length string as well, and this suppresses the
"Tablespace:" field. Patch attached.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
Attachment | Content-Type | Size |
---|---|---|
pg_dump.diff | text/x-diff | 644 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2015-04-29 00:14:11 | Re: Re: BUG #12990: Missing pg_multixact/members files (appears to have wrapped, then truncated) |
Previous Message | Alvaro Herrera | 2015-04-28 23:13:04 | Re: Re: BUG #12990: Missing pg_multixact/members files (appears to have wrapped, then truncated) |