Tom Lane wrote:
> Peter Wilson <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
>>> Could you show us the unmodified output from pg_restore -l, as well as
>>> the edits you made to produce the -L script?
>
>> Raw output from pg_restore -l is as follows:
>
> Hm, this shows only data entries. Was th
Peter Wilson <[EMAIL PROTECTED]> writes:
> Partly the question might be 'what does the error message mean?' - it
> almost looks like do_restore doesn't think it has a real file underneath
> it, instead something that only provides sequential access.
That is certainly what the code thinks; as to wh
Tom Lane wrote:
> Peter Wilson <[EMAIL PROTECTED]> writes:
>
>> Tom Lane wrote:
>>
>>> Could you show us the unmodified output from pg_restore -l, as well as
>>> the edits you made to produce the -L script?
>>>
>
>
>> Raw output from pg_restore -l is as follows:
>>
>
> Hm, th
Peter Wilson <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Could you show us the unmodified output from pg_restore -l, as well as
>> the edits you made to produce the -L script?
> Raw output from pg_restore -l is as follows:
Hm, this shows only data entries. Was the original pg_dump made with
Peter Wilson <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Could you show us the unmodified output from pg_restore -l, as well as
>> the edits you made to produce the -L script?
> Raw output from pg_restore -l is as follows:
Hm, only data entries? What options did you use in the original
pg_d
Tom Lane wrote:
> Peter Wilson <[EMAIL PROTECTED]> writes:
>> pg_restore : [custom archiver] Dumping a specific TOC data block out of
>> order is
>> not supported without ID on this input stream (fseek required).
>
> Could you show us the unmodified output from pg_restore -l, as well as
> the edi
I'm sorry, but I have experiences only with LATNI2 and WIN1250 databases
on PostgreSQL 8.0.3, 8.0.6, 8.0.7, 8.1.3 .
I'm afraid, that without having Your SQL script file Your problem can be
difficult to resolve.
Adam
Jessica Richard wrote:
can you please be more specific?
I used pg_dump db to
Peter Wilson <[EMAIL PROTECTED]> writes:
> pg_restore : [custom archiver] Dumping a specific TOC data block out of order
> is
> not supported without ID on this input stream (fseek required).
Could you show us the unmodified output from pg_restore -l, as well as
the edits you made to produce the
I had problems, like that. I've omitted them using "plain" format (SQL
script file) of dump file. I restore data from "plain" format with psql
- using command "\i FILE". It work always. If You gzip this "plain" file
- You become simillar volume of file using binary dump format.
Greetings
Adam
