Re: BUG #5959: pg_restore --use-list does not always work with a pg_restore generated TOC file

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Per-Olov Esgard <Per-Olov(dot)Esgard(at)micronic-mydata(dot)com>
Cc: pgsql-bugs(at)postgreSQL(dot)org
Subject: Re: BUG #5959: pg_restore --use-list does not always work with a pg_restore generated TOC file
Date: 2011-04-07 15:44:25
Message-ID: 14343.1302191065@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> Per-Olov Esgard <Per-Olov(dot)Esgard(at)micronic-mydata(dot)com> writes:
>> The third extracted buffer is not ok but interpreted as ok with id 10:
>> 10."boolean", mydbcomndata_10."boolean", mydbcomndata_10."boolean",
>> mydbcomndata_10."boolean", mydbcomndata_10."boolean", character varying,
>> mydbcomndata_10."integer", mydbcomndata_10.componentname,
>> mydbcomndata_10."integer", mydbcomndata_10."integer",
>> mydbcomndata_10."integer", mydbcomndata_10.angle,
>> mydbcomndata_10."boolean", mydbcomndata_10."boolean",
>> mydbcomndata_10."boolean", mydbcomndata_10."boolean",
>> mydbcomndata_10."boolean", mydbcomndata_10."boolean",
>> mydbcomndata_10."boolean") postgres

>> So as you can see, the last part of my schema name consists of a number
>> that is interpreted as an id.

> Ah, I see. So what we probably need to do for a real fix is to teach
> that code to distinguish continuation lines from normal ones.

Fix committed --- thanks for the report!

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message John R Pierce 2011-04-07 17:11:05 Re: BUG #5967: Db maintainace
Previous Message Alvaro Herrera 2011-04-07 14:16:12 Re: Failed assert ((data - start) == data_size) in heaptuple.c