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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Albert Ullrich <aullrich(at)blackducksoftware(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5626: Parallel pg_restore fails with "tuple concurrently updated"
Date: 2010-08-20 18:19:17
Message-ID: 23980.1282328357@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)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.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2010-08-20 19:47:03 Re: COPY FROM/TO losing a single byte of a multibyte UTF-8 sequence
Previous Message Stephen Frost 2010-08-20 17:43:40 Re: BUG #5626: Parallel pg_restore fails with "tuple concurrently updated"