Re: [GENERAL] pg_restore error -- missing pg table

2017-09-11 Thread
--- t...@sss.pgh.pa.us wrote: From: Tom Lane <t...@sss.pgh.pa.us> To: "" <kbran...@pwhome.com> cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] pg_restore error -- missing pg table Date: Mon, 11 Sep 2017 13:43:16 -0400 "" <kbran...@pwhome.com> writ

Re: [GENERAL] pg_restore error -- missing pg table

2017-09-11 Thread Tom Lane
"" writes: > /opt/pgsql-9.5/bin/pg_restore -v --clean --create --dbname=nms > --schema=public . > ... > pg_restore: [archiver (db)] could not execute query: ERROR: function > _pg_sv_column_array(oid, smallint[]) does not exist > LINE 6: _pg_sv_column_array(k1.conrelid,

[GENERAL] pg_restore error -- missing pg table

2017-09-11 Thread
We've been doing backups and restores with many tests and uses and never had a problem until now. Sadly, I'm not sure where to even begin looking to figure out what to do, so any pointers would be very much appreciated! The vital stats: Pg: 9.5.1 (this will get upgraded to 10.0 when it's

Re: [GENERAL] pg_restore error-s after pg_dump

2016-06-22 Thread Adrian Klaver
On 06/22/2016 04:00 AM, SDAG wrote: Hi Postgres version : *PostgreSQL 9.2.4 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-3), 64-bit* We transfer from one server to another (with better cpu an ram) our system using vm converter and when I try to backup

[GENERAL] pg_restore error-s after pg_dump

2016-06-22 Thread SDAG
Hi Postgres version : *PostgreSQL 9.2.4 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-3), 64-bit* We transfer from one server to another (with better cpu an ram) our system using vm converter and when I try to backup database have an error : *pg_dump: reading

Re: [GENERAL] pg_restore error with out of memory

2012-12-14 Thread AI Rumman
I modified the shared_buffer=50 MB and maintenance_work_mem = 50 MB But still getting the same error. On Thu, Dec 13, 2012 at 7:36 PM, Kevin Grittner kgri...@mail.com wrote: AI Rumman wrote: I am going to restore a 6 Gb database in my development machine which is running on Centos 5.6 with

Re: [GENERAL] pg_restore error with out of memory

2012-12-14 Thread Kevin Grittner
AI Rumman wrote: I modified the shared_buffer=50 MB and maintenance_work_mem = 50 MB But still getting the same error. I hope you restarted the PostgreSQL server? If so, pg_restore might just need more RAM than that machine has to deal with that particular database. You might try a text

[GENERAL] pg_restore error with out of memory

2012-12-13 Thread AI Rumman
I am going to restore a 6 Gb database in my development machine which is running on Centos 5.6 with memory 1 GB. During restoration I got error as follows: LOG: checkpoints are occurring too frequently (22 seconds apart) HINT: Consider increasing the configuration parameter

Re: [GENERAL] pg_restore error with out of memory

2012-12-13 Thread Kevin Grittner
AI Rumman wrote: I am going to restore a 6 Gb database in my development machine which is running on Centos 5.6 with memory 1 GB. pg_restore: out of memory pg_restore: finished item 8570 TABLE DATA entity pg_restore: [archiver] worker process failed: exit code 1 I set postgresql.conf as -

Re: [GENERAL] pg_restore error - Any Idea?

2009-03-23 Thread Erik Jones
On Mar 22, 2009, at 10:44 PM, DM wrote: Hi All, I am facing an error on executing the below command dump name: pg_dump_FcZ0.pnps_200903041201_1.2.1.0_base_testing databae name: pnqd_test $pg_restore -U postgres -p 5433 -d pnqd_test pg_dump_FcZ0.pnps_200903041201_1.2.1.0_base_testing

Re: [GENERAL] pg_restore error - Any Idea?

2009-03-23 Thread DM
Eric, There was no change in the version, we are using postgres v8.3.5 Thanks Deepak On Sun, Mar 22, 2009 at 11:17 PM, Erik Jones ejo...@engineyard.com wrote: On Mar 22, 2009, at 10:44 PM, DM wrote: Hi All, I am facing an error on executing the below command dump name:

[GENERAL] pg_restore error - Any Idea?

2009-03-22 Thread DM
Hi All, I am facing an error on executing the below command dump name: pg_dump_FcZ0.pnps_200903041201_1.2.1.0_base_testing databae name: pnqd_test $pg_restore -U postgres -p 5433 -d pnqd_test pg_dump_FcZ0.pnps_200903041201_1.2.1.0_base_testing pg_restore: [archiver (db)] Error while PROCESSING

[GENERAL] pg_restore error

2006-11-27 Thread Peter Wilson
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 required). The command was : pg_restore -L /tmp/toc --dbname=whitebeam --disable-triggers

Re: [GENERAL] pg_restore error

2005-12-02 Thread Scott Frankel
Using custom output format instead of tar output (-Fc instead if -Ft) appears to work without error. My initial tests with the backup db seem to match the original db. The compressed output files are also a lot smaller ;) Note that the problematic tar files were never transfered between

[GENERAL] pg_restore error

2005-12-01 Thread Scott Frankel
What does this error mean? pg_restore: [tar archiver] could not find header for file 1765.dat in tar archive All of a sudden, I'm encountering this error as I debug a problem with the db interface I'm using. My backups are created using a script that hasn't changed recently, though I

Re: [GENERAL] pg_restore error

2005-12-01 Thread Tom Lane
Scott Frankel [EMAIL PROTECTED] writes: What does this error mean? pg_restore: [tar archiver] could not find header for file 1765.dat in tar archive It means either the tar file is corrupt or pg_restore has a bug. Can tar read the file correctly? If so, does it find a file named

Re: [GENERAL] pg_restore error

2005-12-01 Thread Scott Frankel
Yes, the tar file contains a file called 1765.dat. A `cat` of that file shows nothing more than an empty line (i.e.: a carriage return). -rw--- 1 frankel prod1 Nov 29 11:20 1765.dat Extracting the archive, tar reported a lone zero block. I don't know what this

Re: [GENERAL] pg_restore error

2005-12-01 Thread Tom Lane
Scott Frankel [EMAIL PROTECTED] writes: Yes, the tar file contains a file called 1765.dat. A `cat` of that file shows nothing more than an empty line (i.e.: a carriage return). -rw--- 1 frankel prod1 Nov 29 11:20 1765.dat Extracting the archive, tar reported a lone

[GENERAL] pg_restore error

2005-09-29 Thread Partners - Majolee InfoTech
Hello, We use i686 based linux RH9.0 system and our postgresql is 8.0.3 We use following command su -c '/usr/local/pgsql/bin/pg_dump -d -O -x[DBNAME] [file withpath]' postgres to generate dump. But while restoring it gives too many errors and that is because it uses $_$ for plpgsql

Re: [GENERAL] pg_restore error

2005-09-29 Thread Richard Huxton
Partners - Majolee InfoTech wrote: Hello, We use i686 based linux RH9.0 system and our postgresql is 8.0.3 But while restoring it gives too many errors and that is because it uses $_$ for plpgsql function body separator which the pg_restore and psql [dbname] [file] both does not seem to

[GENERAL] pg_restore error

2005-03-11 Thread go
Hi All! While restoring PG7.23 dump into PG 8.01 database (pg_restore -Fc -d a3 -v arz3.test.dat) i got error: pg_restore: ERROR: invalid byte sequence for encoding UNICODE: 0xfc3535 CONTEXT: COPY mytable, line 9, column post3: 55146/23.12.04 pg_restore: [archiver (db)]

Re: [GENERAL] pg_restore error

2005-03-11 Thread Richard Huxton
go wrote: Hi All! While restoring PG7.23 dump into PG 8.01 database (pg_restore -Fc -d a3 -v arz3.test.dat) i got error: pg_restore: ERROR: invalid byte sequence for encoding UNICODE: 0xfc3535 CONTEXT: COPY mytable, line 9, column post3: 55146/23.12.04 pg_restore: [archiver

Re: [GENERAL] pg_restore: error returned by PQputline

2004-09-02 Thread Clodoaldo Pinto Neto
--- Tom Lane [EMAIL PROTECTED] escreveu: the only mechanism I've heard of that causes this is the Linux kernel's out-of-memory killer --- see http://www.postgresql.org/docs/7.4/static/kernel-resources.html#AEN17068 Googling for OOM kill will give you additional gory details :-(. I

Re: [GENERAL] pg_restore: error returned by PQputline

2004-09-02 Thread Tom Lane
=?iso-8859-1?q?Clodoaldo=20Pinto=20Neto?= [EMAIL PROTECTED] writes: --- Tom Lane [EMAIL PROTECTED] escreveu: Googling for OOM kill will give you additional gory details :-(. I did: # /sbin/sysctl -w vm.overcommit_memory=2 vm.overcommit_memory = 2 But it didn't help much: