Hi, Thanks for the answer. I've checked and the archive is corrupted. Every time I dump my database with pg_dump command mentioned in the previous post, I've got the same error. Could you please suggest me other compination of parameters for pg_dump, so that it dumps complete database (inluding functions, triggers, procedures, operators, sequences, tables, views etc. and obviously data)? It doesn't have to be stored in .tar archive. Moreover I'd like to inform that I work in Windows environment. Looking forward the answer. BR, Rafal Tom Lane-2 wrote: > > rafikoko <rako@xxxxxxxxxx> writes: >> I've got also the following message after dumping: >> pg_dump: [tar archiver] actual file length (4104361) does not match >> expected >> (4104361) >> which in fact does not make sense for me. > > Hmm, it looks like that code is printing the wrong variable's value. > However, the condition it's complaining of shouldn't have happened, > so you need to look more closely. I suspect you've got a corrupt > tar archive. Does it look sane if you do "tar tvf" on it? > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster > > -- View this message in context: http://www.nabble.com/pg_dump....-pg_restore...how-long-does-it-take--tf4347124.html#a12402596 Sent from the PostgreSQL - general mailing list archive at Nabble.com. ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
