[ADMIN] Problem restoring with pg_dump

I posted this to 'general' yesterday but with no luck. This is probably a better group. I've just got the following message while trying to restore a database : pg_restore : [custom archiver] Dumping a specific TOC data block out of order is not supported without ID on this input stream (fseek re

[ADMIN] how do I create a db with unicode encoding on a utf8 server

I have a Postgre server with UTF8 as the default encoding. I am trying to create a new database on this same server with UNICODE encoding so that I can load an UNICODE database from another server. No matter how I specify unicode option on this utf8 server, it just created a utf8 db for me any

[ADMIN] how do I load a 8.0.8 database with unicode encoding into 8.1.4/utf8?

got an errro when loading a db from 8.0.8 with unicode to 8.1.4 server with UTF8 server: ERROR: invalid byte sequence for encoding "UTF8": 0x92 thanks, Jessica - Everyone is raving about the all-new Yahoo! Mail beta.

Re: [ADMIN] Problem restoring with pg_dump

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

Re: [ADMIN] Problem restoring with pg_dump

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

Re: [ADMIN] how do I load a 8.0.8 database with unicode encoding

On Tue, 28 Nov 2006, Jessica Richard wrote: got an errro when loading a db from 8.0.8 with unicode to 8.1.4 server with UTF8 server: ERROR: invalid byte sequence for encoding "UTF8": 0x92 See this info in the HISTORY file: * Some users are having problems loading UTF-8 data into 8.1.X

[ADMIN] FATAL message in log

Hello, I am getting the following message in the log. I am trying to find out what does it mean ? 2006-11-15 23:33:22 PST[unknown]md11.16.154.140FATAL: invalid startup packet layout: expected terminator as last byte Thanks Abu - Sponsored Link Mortgage rate

Re: [ADMIN] FATAL message in log

My first guess is to check the versions / compatibility of your client and server. --Imad www.EnterpriseDB.com On 11/28/06, Abu Mushayeed <[EMAIL PROTECTED]> wrote: Hello, I am getting the following message in the log. I am trying to find out what does it mean ? 2006-11-15 23:33:22 PST[unknow

Re: [ADMIN] FATAL message in log

Abu Mushayeed <[EMAIL PROTECTED]> writes: > I am getting the following message in the log. I am trying to find out what > does it mean ? > 2006-11-15 23:33:22 PST[unknown]md11.16.154.140FATAL: invalid startup packet > layout: expected terminator as last byte It means the client sent an incorre

Re: [ADMIN] Problem restoring with pg_dump

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

Re: [ADMIN] Problem restoring with pg_dump

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

Re: [ADMIN] Problem restoring with pg_dump

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