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

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 Mon

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 wrote: > On 07/27/2015 10:55 AM, AI Rumman wrote: > >> No it is "-s" for schema only backup. >> > > M

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 mailto:adrian.kla...@aklaver.com>> wrote: On 0

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 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: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 mi

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

Louis > >From: Craig Ringer >To: "mailtolouis2020-postg...@yahoo.com" >Cc: Postgres >Sent: Saturday, October 29, 2011 5:05 PM >Subject: Re: [GENERAL] PG_DUMP error : unexpected chunk number > >On 10/28/2011 06:24 PM, mailtolouis2020-postg...@ya

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 4)

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" 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 Allyt

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? > > Regards > > Gastón Quiroga > Allytech S.A. > > Tom Lane wrote: > > =?ISO-8859-1?Q?Gast=F3n?= writes: > > It'

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

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?= writes: It's Postgres version 8.0.8 Well, that's pretty a

Re: [GENERAL] pg_dump ERROR, usename "postgres" duplicated

=?ISO-8859-1?Q?Gast=F3n?= 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 WHERE on ctid.

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?= writes: I checked the pg_user database and I found this: postgres=# select * from pg_use

Re: [GENERAL] pg_dump ERROR, usename "postgres" duplicated

=?ISO-8859-1?Q?Gast=F3n_Quiroga?= 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: 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

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 conce

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 time,

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 - 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 broadcast)--

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 ou

Re: [GENERAL] pg_dump error codes

Here is a simple one, that keeps 2 copies (one for odd-numbered days and one for even-numbered days), and emails the admin with the status: #!/bin/sh #This script is to back up the production databases DBLIST="db1 proddb1 proddb2" PGUSER=dbusername DUMPDIR=/disk1/database/backups MAILCMD=/bin/m

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

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: 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 synchro

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 >

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 act

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

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 e

Re: [GENERAL] pg_dump error - LOCALIZATION PROBLEM

>> 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? Wait a minute --- I spoke too quickly. The lexer's behavior is to downcase unquoted identifiers in a *locale sensitive*

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 strcasecm

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_SERIALIZ

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

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