Christian Reis wrote:
> Public bug reported:
>
> When merging two users on production, I ran into consistent timeouts on
> these two queries:
>
> UPDATE POSubmission SET person=1457193 WHERE person=299986
> (2218 rows)
>
> UPDATE pomsgset SET reviewer=1457193 WHERE reviewer=299986
> (1473 rows)
>
> I'm wondering if the DB schema change that will be done to fix bug 30602
> will address this.
With the current database design I think we have to accept that there will
always be some cases where the people merge will fail. We could fix this
with a fairly radical db schema refactoring, adding a layer of indirection,
but I'm not sure that would be a step forward.
I think we need to customize the timeout page for people merge, so if it
times out the user is requested to open a support request so we can do it
manually.
Christian Reis wrote:
> Public bug reported:
>
> When merging two users on production, I ran into consistent timeouts on
> these two queries:
>
> UPDATE POSubmission SET person=1457193 WHERE person=299986
> (2218 rows)
>
> UPDATE pomsgset SET reviewer=1457193 WHERE reviewer=299986
> (1473 rows)
>
> I'm wondering if the DB schema change that will be done to fix bug 30602
> will address this.
With the current database design I think we have to accept that there will
always be some cases where the people merge will fail. We could fix this
with a fairly radical db schema refactoring, adding a layer of indirection,
but I'm not sure that would be a step forward.
I think we need to customize the timeout page for people merge, so if it
times out the user is requested to open a support request so we can do it
manually.
-- www.canonical. com/ www.ubuntu. com/
Stuart Bishop <email address hidden> http://
Canonical Ltd. http://