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-02 22:41:21
Message-ID: 1843.1301784081@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Per-Olov Esgard" <Per-Olov(dot)Esgard(at)micronic-mydata(dot)com> writes:
> Description: pg_restore --use-list does not always work with a
> pg_restore generated TOC file
> Details:

> General
> =======
> In my application I am using automatically generated psm:s. These psm: are
> using many arguments, in some cases over 80. This means that a TOC entry in
> a TOC file generated by pg_restore --list may be very long for psm:s with
> such a long signature.

> Specific
> ========
> My backup system makes a schema dump to a file and a data dump to another
> file. When performing a restore I create a TOC list from the schema dump by
> using pg_restore on the schema dump file. I do some filtering on the TOC
> file and then I restore it using pg_restore --use-list. This does not work
> since some entries in the TOC file are more than 2000 characters long. The
> function SortTocFromFile in pg_backup_archiver.c has a hard coded limitation
> of 1024 characters for each row in the TOC file.

Hm. The function only cares about the dump ID at the start of the line.
AFAICS the consequence of buffer overflow would be that it'd take a line
continuation as a new line; which would generally result in a harmless
"WARNING: line ignored" message. You didn't say exactly what symptom
you were seeing, but "does not work" seems like a bit of an
overstatement for that. So I'm wondering whether you're seeing some
behavior I'm missing.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Chris Curvey 2011-04-03 00:44:50 BUG #5964: doc bug -- copy does not take "format" literal
Previous Message Gavin Flower 2011-04-02 05:41:17 BUG #5963: make -j4 check fails