Re: [BUGS] BUG #5626: Parallel pg_restore fails with "tuple concurrently updated"

2010-08-25 Thread Albert Ullrich
I followed your advise, Tom and reworked the way we do dumps and restores to remove the requirement for having TOCs. So far the restores executed flawlessly and I am grateful for having this feature available to us! Huge time savings! Thanks! Albert On 8/20/10 1:24 PM, "Tom Lane" wrote: Al

Re: [BUGS] BUG #5626: Parallel pg_restore fails with "tuple concurrently updated"

2010-08-21 Thread Tom Lane
I wrote: > We should probably try to make pg_restore smarter about this case, I've applied a patch for this: http://archives.postgresql.org/pgsql-committers/2010-08/msg00271.php regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make cha

Re: [BUGS] BUG #5626: Parallel pg_restore fails with "tuple concurrently updated"

2010-08-20 Thread Tom Lane
Stephen Frost writes: > * Tom Lane (t...@sss.pgh.pa.us) wrote: >> We should probably try to make pg_restore smarter about this case, > Yes, definitely. I don't have an immediate solution though, I just posted some further analysis to pgsql-hackers. Please follow up there.

Re: [BUGS] BUG #5626: Parallel pg_restore fails with "tuple concurrently updated"

2010-08-20 Thread Stephen Frost
* Tom Lane (t...@sss.pgh.pa.us) wrote: > Mph ... removing the public schema from the restore list is problematic, > because you've got a lot of stuff *in* the public schema, and of course > all that stuff depends on the public schema entry. Normally this > doesn't bother pg_restore because it just

Re: [BUGS] BUG #5626: Parallel pg_restore fails with "tuple concurrently updated"

2010-08-20 Thread Tom Lane
Albert Ullrich writes: > We run essentially the following commands to create the table of contents in > order to prevent pg_restore from failing: > pg_restore -l database.dump | \ > eval fgrep -v -e "' SCHEMA - public '" \ > -e "' COMMENT - SCHEMA public '" \ > -e "' PROCEDURAL LANGUA

Re: [BUGS] BUG #5626: Parallel pg_restore fails with "tuple concurrently updated"

2010-08-19 Thread Albert Ullrich
We run essentially the following commands to create the table of contents in order to prevent pg_restore from failing: pg_restore -l database.dump | \ eval fgrep -v -e "' SCHEMA - public '" \ -e "' COMMENT - SCHEMA public '" \ -e "' PROCEDURAL LANGUAGE - plpgsql'" database.toc Where w

Re: [BUGS] BUG #5626: Parallel pg_restore fails with "tuple concurrently updated"

2010-08-19 Thread Tom Lane
"Albert Ullrich" writes: > Description:Parallel pg_restore fails with "tuple concurrently > updated" > pg_restore -e -v -j 4 -Fc -L /tmp/fp_basic.toc -d fp_basic > /tmp/fp_basic.dump Apparently you've used the -L option to reorder the dump objects in a way that won't work with parallel

[BUGS] BUG #5626: Parallel pg_restore fails with "tuple concurrently updated"

2010-08-18 Thread Albert Ullrich
The following bug has been logged online: Bug reference: 5626 Logged by: Albert Ullrich Email address: aullr...@blackducksoftware.com PostgreSQL version: 8.4.4 Operating system: Centos 5.5 64bit Description:Parallel pg_restore fails with "tuple concurrently updated" D