Re: [GENERAL] pg_dump - ERROR - PostgreSQL 9.2

[SOLVED] Just to let you guys know.. I've solved this issue changing the max_standby_streaming_delay on my slave to "-1". Cheers Lucas Possamai - kinghost.co.nz - DigitalOcean

[GENERAL] pg_dump - ERROR - PostgreSQL 9.2

Hi all, *masterdb01 -> slave01 -> slave02 -> slave03* *testmaster01 (Full copy from masterdb01)* I'm trying to refresh my main DB, by running this command on my test server: ssh postgres@slave02 "/usr/pgsql-9.2/bin/pg_dump > --exclude-table-data='junk.*' --format=custom master_db_name" | >

Re: [GENERAL] pg_dump error

I am not using any comma here. With the same command I am able to take dump on other disks. But with ISOLON CIFS, I am getting the error. Thanks. On Mon, Jul 27, 2015 at 10:56 AM, Adrian Klaver adrian.kla...@aklaver.com wrote: On 07/27/2015 10:55 AM, AI Rumman wrote: No it is -s for schema

[GENERAL] pg_dump error

Hi, I am getting the following error during pg_dump: pg_dump dbname -v -t tablename -s -Fc -f dbname_tablename,sqlc pg_dump: [custom archiver] WARNING: ftell mismatch with expected position -- ftell used I am using Postgresql 9.1 and I have enough disk space on it. The backup drive is on

Re: [GENERAL] pg_dump error

On 07/27/2015 10:58 AM, AI Rumman wrote: I am not using any comma here. With the same command I am able to take dump on other disks. I beg to differ, From your original post: -f dbname_tablename,sqlc ^^^ But with ISOLON CIFS, I am getting the error. Thanks. On

Re: [GENERAL] pg_dump error

On 07/27/2015 10:48 AM, AI Rumman wrote: Hi, I am getting the following error during pg_dump: pg_dump dbname -v -t tablename -s -Fc -f dbname_tablename,sqlc ^ Is that really a ','(comma)? pg_dump: [custom archiver] WARNING: ftell

Re: [GENERAL] pg_dump error

No it is -s for schema only backup. Thanks. On Mon, Jul 27, 2015 at 10:53 AM, Adrian Klaver adrian.kla...@aklaver.com wrote: On 07/27/2015 10:48 AM, AI Rumman wrote: Hi, I am getting the following error during pg_dump: pg_dump dbname -v -t tablename -s -Fc -f dbname_tablename,sqlc

Re: [GENERAL] pg_dump error

On 07/27/2015 10:55 AM, AI Rumman wrote: No it is -s for schema only backup. My ^ got misplaced in sending. I was talking about the ',' in the file name at the end of the command. Thanks. On Mon, Jul 27, 2015 at 10:53 AM, Adrian Klaver adrian.kla...@aklaver.com

[GENERAL] pg_dump error

Hi, I am using PostgreSQL 9.0. It is installed on Windows XP. I am trying to take a backup of the database using pg_dump. But each time I give a command Pg_dump pgdb backup.sql I am prompted for a password and I provided the database password. After this, I got an error as follows..

Re: [GENERAL] pg_dump error

On 11/17/11 11:01 PM, mamatha_kagathi_c...@dell.com wrote: I am using PostgreSQL 9.0. It is installed on Windows XP. I am trying to take a backup of the database using pg_dump. But each time I give a command Pg_dump pgdb backup.sql I am prompted for a password and I provided the database

Re: [GENERAL] PG_DUMP error : unexpected chunk number

From: Craig Ringer ring...@ringerc.id.au To: mailtolouis2020-postg...@yahoo.com mailtolouis2020-postg...@yahoo.com Cc: Postgres pgsql-general@postgresql.org Sent: Saturday, October 29, 2011 5:05 PM Subject: Re: [GENERAL] PG_DUMP error : unexpected chunk number On 10/28/2011 06

Re: [GENERAL] PG_DUMP error : unexpected chunk number

On 10/28/2011 06:24 PM, mailtolouis2020-postg...@yahoo.com wrote: Hello, I think I got a big problem now, I'm not able to do pg_dump on one of my production database. When I do pg_dump it give me this error: pg_dump: Error message from server: ERROR: unexpected chunk number 18390760 (expected

[GENERAL] PG_DUMP error : unexpected chunk number

Hello, I think I got a big problem now, I'm not able to do pg_dump on one of my production database. When I do pg_dump it give me this error: pg_dump: Error message from server: ERROR:  unexpected chunk number 18390760 (expected 4) for toast value 92784 in pg_toast_88487 I believe this

[GENERAL] pg_dump error unexpected chunk number

Hello, I think I got a big problem now, I'm not able to do pg_dump on one of my production database. When I do pg_dump it give me this error: pg_dump: Error message from server: ERROR:  unexpected chunk number 18390760 (expected 4) for toast value 92784 in pg_toast_88487 I believe this

[GENERAL] pg_dump: Error message from server: ERROR: canceling statement due to conflict with recovery

pg_dump: SQL command failed pg_dump: Error message from server: ERROR: canceling statement due to conflict with recovery DETAIL: User query might have needed to see row versions that must be removed. pg_dump: The command was: COPY public.i.. TO stdout; pg_dumpall: pg_dump failed on database

Re: [GENERAL] pg_dump ERROR, usename postgres duplicated

The upgrade works, thank you all ! Gastón Quiroga Allytech S.A. Adrian Klaver wrote: - Gastón Quiroga gast...@allytech.com wrote: Thank You Tom: I'll Try to make an update, but the 2 fields are equals row by row, how could I make a difference in the WHERE statement? Regards

Re: [GENERAL] pg_dump ERROR, usename postgres duplicated

Thank You Tom: I'll Try to make an update, but the 2 fields are equals row by row, how could I make a difference in the WHERE statement? Regards Gastón Quiroga Allytech S.A. Tom Lane wrote: =?ISO-8859-1?Q?Gast=F3n?= ta...@allytech.com writes: It's Postgres version 8.0.8

Re: [GENERAL] pg_dump ERROR, usename postgres duplicated

Gastón Quiroga wrote: Thank You Tom: I'll Try to make an update, but the 2 fields are equals row by row, how could I make a difference in the WHERE statement? Use the ctid hidden system field. -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL

Re: [GENERAL] pg_dump ERROR, usename postgres duplicated

- Gastón Quiroga gast...@allytech.com wrote: Thank You Tom: I'll Try to make an update, but the 2 fields are equals row by row, how could I make a difference in the WHERE statement? Regards Gastón Quiroga Allytech S.A. Tom Lane wrote: =?ISO-8859-1?Q?Gast=F3n?=

[GENERAL] pg_dump ERROR, usename postgres duplicated

Hi: I cannot dump any database from my server. When I try to do it i receive this error pg_dump: The command was: SELECT tableoid, oid, nspname, (select usename from pg_user where nspowner = usesysid) as usename, nspacl FROM pg_namespace I checked the pg_user database and I found

[GENERAL] pg_dump ERROR, usename postgres duplicated

Hi: I cannot dump any database from my server. When I try to do it i receive this error pg_dump: The command was: SELECT tableoid, oid, nspname, (select usename from pg_user where nspowner = usesysid) as usename, nspacl FROM pg_namespace I checked the pg_user database and I found

[GENERAL] pg_dump ERROR, usename postgres duplicated

Hi: I cannot dump any database from my server. When I try to do it i receive this error pg_dump: The command was: SELECT tableoid, oid, nspname, (select usename from pg_user where nspowner = usesysid) as usename, nspacl FROM pg_namespace I checked the pg_user database and I found

Re: [GENERAL] pg_dump ERROR, usename postgres duplicated

=?ISO-8859-1?Q?Gast=F3n_Quiroga?= gast...@allytech.com writes: I checked the pg_user database and I found this: postgres=# select * from pg_user; usename| usesysid | usecreatedb | usesuper | usecatupd | passwd | valuntil | useconfig

Re: [GENERAL] pg_dump ERROR, usename postgres duplicated

Thanks for your reply Tom, and sorry for the duplicated e-mails. It's Postgres version 8.0.8 Thank you Gastón Quiroga Allytech S.A. Tom Lane wrote: =?ISO-8859-1?Q?Gast=F3n_Quiroga?= gast...@allytech.com writes: I checked the pg_user database and I found this: postgres=#

Re: [GENERAL] pg_dump ERROR, usename postgres duplicated

=?ISO-8859-1?Q?Gast=F3n?= ta...@allytech.com writes: It's Postgres version 8.0.8 Well, that's pretty ancient, and I see at least one bug in the release history that could result in duplicated rows. I'd counsel an update to 8.0.something-recent. You can probably delete the extra row using a

[GENERAL] pg_dump: ERROR: could not open relation with OID ...

During a routine backup procedure (that does not run nightly) for an 8.2.3 postgres cluster, pg_dump failed: pg_dump: Error message from server: ERROR: could not open relation with OID ... In doing some log forensics, I discovered that this error has been showing up in the logs

Re: [GENERAL] pg_dump: ERROR: could not open relation with OID ...

Thomas F. O'Connell wrote: During a routine backup procedure (that does not run nightly) for an 8.2.3 postgres cluster, pg_dump failed: pg_dump: Error message from server: ERROR: could not open relation with OID ... In doing some log forensics, I discovered that this error has been

Re: [GENERAL] pg_dump error - filesystem full

Try export TMPDIR=/var/tmp. Also, unless you have a really good reason to be using -Ft dump format, I'd recommend -Fc format instead. It's better tested and doesn't suffer from various limitations of the tar format, notably the need for a temp file. Thanks, it takes much longer

Re: [GENERAL] pg_dump error - filesystem full

=?ISO-8859-1?Q?Poul_M=F8ller_Hansen?= [EMAIL PROTECTED] writes: Also, unless you have a really good reason to be using -Ft dump format, I'd recommend -Fc format instead. Thanks, it takes much longer time, but the filesize is only 1/5 of the tar size, so it's ok. If you're more concerned

[GENERAL] pg_dump error - filesystem full

/tmp: write failed, filesystem is full pg_dump: [tar archiver] could not write to tar member (wrote 0, attempted 101) Is there a way to make pg_dump use /var/tmp as a temporary filespace instead ? Thanks, Poul ---(end of broadcast)--- TIP

Re: [GENERAL] pg_dump error - filesystem full

Am Dienstag, 7. März 2006 11:13 schrieb Poul Møller Hansen: Is there a way to make pg_dump use /var/tmp as a temporary filespace instead ? Try export TMPDIR=/var/tmp. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of

Re: [GENERAL] pg_dump error - filesystem full

Peter Eisentraut [EMAIL PROTECTED] writes: Am Dienstag, 7. März 2006 11:13 schrieb Poul Møller Hansen: Is there a way to make pg_dump use /var/tmp as a temporary filespace instead ? Try export TMPDIR=/var/tmp. Also, unless you have a really good reason to be using -Ft dump format, I'd

Re: [GENERAL] pg_dump error codes

: Sent by: Subject: [GENERAL] pg_dump error codes

Re: [GENERAL] pg_dump error codes

Michael Fuhr wrote: On Mon, Jan 02, 2006 at 08:45:28AM -0200, alexandre - aldeia digital wrote: In my Linux bash backup scripts, I wish to send an e-mail when an error occurs in pg_dump proccess. And if possible, I want to send the error output via e-mail. Anybody knows how to capture the

[GENERAL] pg_dump error codes

Hi, (maybe an idiot question) In my Linux bash backup scripts, I wish to send an e-mail when an error occurs in pg_dump proccess. And if possible, I want to send the error output via e-mail. Anybody knows how to capture the output and send this to an e-mail ONLY if an error occurs ?

Re: [GENERAL] pg_dump error codes

On Mon, 2 Jan 2006, alexandre - aldeia digital wrote: In my Linux bash backup scripts, I wish to send an e-mail when an error occurs in pg_dump proccess. And if possible, I want to send the error output via e-mail. Anybody knows how to capture the output and send this to an e-mail ONLY if an

Re: [GENERAL] pg_dump error codes

On Mon, Jan 02, 2006 at 08:45:28AM -0200, alexandre - aldeia digital wrote: In my Linux bash backup scripts, I wish to send an e-mail when an error occurs in pg_dump proccess. And if possible, I want to send the error output via e-mail. Anybody knows how to capture the output and send this

[GENERAL] pg_dump: ERROR: Memory exhausted in AllocSetAlloc(875574064)

Is there any solution to this other than adding memory, or am I mis-understanding the error? pg_dump: ERROR: Memory exhausted in AllocSetAlloc(875574064) pg_dump: lost synchronization with server, resetting connection pg_dump: SQL command to dump the contents of table table_name failed:

Re: [GENERAL] pg_dump: ERROR: Memory exhausted in AllocSetAlloc(875574064)

Reid Thompson [EMAIL PROTECTED] writes: Is there any solution to this other than adding memory, or am I mis-understanding the error? pg_dump: ERROR: Memory exhausted in AllocSetAlloc(875574064) pg_dump: lost synchronization with server, resetting connection My bet is that this is actually a

Re: [GENERAL] pg_dump: ERROR: Memory exhausted in AllocSetAlloc(875574064)

Tom Lane wrote: Reid Thompson [EMAIL PROTECTED] writes: Is there any solution to this other than adding memory, or am I mis-understanding the error? pg_dump: ERROR: Memory exhausted in AllocSetAlloc(875574064) pg_dump: lost synchronization with server, resetting connection My bet is

Re: [GENERAL] pg_dump: ERROR: Memory exhausted in AllocSetAlloc(875574064)

On Thu, May 12, 2005 at 02:56:35PM -0400, Tom Lane wrote: Reid Thompson [EMAIL PROTECTED] writes: Is there any solution to this other than adding memory, or am I mis-understanding the error? pg_dump: ERROR: Memory exhausted in AllocSetAlloc(875574064) pg_dump: lost synchronization with

[GENERAL] pg_dump error

I'm rather new to database stuff. I've been using postgresql for a couple years, but that doesn't mean I understand what I'm doing. I have simply followed the HOW-TOs. But now I think I'm about to learn a bit more about the inner workings... Last week my cron-triggered system-backup began

Re: [GENERAL] pg_dump error

On 23/05/2004 20:32 Philip wrote: [snip] Okay, now I'm stumped! Since I don't even know what pga_images is for I don't no how much trouble I'm in! Should I worry? Am I doomed? Can it be repaired? Will my computer explode and infect my neighborhood? (Have I used too many question-marks?) Nothing

Re: [GENERAL] pg_dump error

Philip [EMAIL PROTECTED] writes: Okay, now I'm stumped! Since I don't even know what pga_images is for I don't no how much trouble I'm in! Not a lot; that's not a system catalog but something that PgAccess creates. If you're not using PgAccess anymore, you can probably just drop the table and

Re: [GENERAL] pg_dump error - LOCALIZATION PROBLEM

Tom Lane writes: Hmm. Given that we expect the lexer to have downcased any unquoted words, this seems like a workable solution --- where else are we using strcasecmp() unnecessarily? I've identified several other such places. However, in reality we have to consider every single

Re: [GENERAL] pg_dump error - LOCALIZATION PROBLEM

Peter Eisentraut [EMAIL PROTECTED] writes: Untested, but try this: Edit src/backend/commands/variable.c, look for the function parse_XactIsoLevel(). Change the code that looks like this: if (strcasecmp(value, SERIALIZABLE) == 0) XactIsoLevel = XACT_SERIALIZABLE;

Ynt: [GENERAL] pg_dump error - LOCALIZATION PROBLEM

Hi, It worked. Thanks a lot. Regards Erol -Özgün Ýleti- Kimden: Peter Eisentraut [EMAIL PROTECTED] Kime: Erol Öz [EMAIL PROTECTED] Bilgi: PostgreSQL General List [EMAIL PROTECTED] Tarih: 14 Eylül 2001 Cuma 18:03 Konu: Re: [GENERAL] pg_dump error - LOCALIZATION PROBLEM Erol Öz writes

Re: [GENERAL] pg_dump error - LOCALIZATION PROBLEM

Erol Öz writes: I think Tom Lane is right as always. My postgresql server was configured with --enable-locale option and it works perfect with Turkish stuff. However I could not find a solution to the problem below. Untested, but try this: Edit src/backend/commands/variable.c, look for the

[GENERAL] pg_dump error

Hi, I get an error when the following command executed; /usr/local/pgsql/bin/pg_dump trollandtoad trollandtoad.out SET TRANSACTION command failed. Explanation from backend: 'ERROR: Bad TRANSACTION ISOLATION LEVEL (serializable) Where should I look at for a solution. Thanks in advance.

[GENERAL] pg_dump error message

Trying to do a dump I get this error: pg_dump -v database backup -- last builtin oid is 1 -- reading user-defined types -- reading user-defined functions -- reading user-defined aggregates getAggregates(): SELECT failed. Explanation from backend: 'ERROR: Attribute 'aggtransfn1' not found

[GENERAL] pg_dump error

I'm trying to back up a table by dumping to a text file, but in the proccess of dumping I get the following error dumpSequence(pilgram_en_id_seq): different sequence name returned by SELECT: pilgram_cross_id_seq I'm not sure what this means, and I have no idea how to corect it. Mike

[GENERAL] pg_dump error

Hello, with pg_dump testdb db.out there is an errorline getTypes(): SELECT failed. Explanation from backend: 'ERROR: cache lookup for userid 201 failed any Idea marc

[GENERAL] pg_dump error: cache lookup failed

Hi, I have a PostgreSQL 6.5.3 database server working flawlessly under Red Hat 6.1 However, when I try to use the pg_dump utility, I get this error: #pg_dump myDatabase backup.db getTypes(): SELECT failed. Explanation from backend: 'ERROR: cache lookup for userid 201 failed

[GENERAL] pg_dump: error in finding the template1 database

I recently upgraded my LinuxPPC system, and to make a long story short I had to re-compile Postgres. Unfortunately I could did not dump my databases out (via pg_dump) to files before I had to recompile Postgres. After Postgres was compiled and restarted, I can access the DATA (mostly) but pg_dump

RE: [GENERAL] pg_dump error

Try vacuum. You could also try dropping and recreating your indexes. -Original Message- From: Stefano Zampieri [SMTP:[EMAIL PROTECTED]] Sent: Saturday, April 03, 1999 3:56 AM To: [EMAIL PROTECTED] Subject:[GENERAL] pg_dump error