Content-Type: text/plain; charset=UTF-8
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: foreign key locks
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Kevin Grittner <kevin.grittner@wicourts.gov>
In-reply-to: <4FEAB90A0200002500048B7D@gw.wicourts.gov>
References: <4FEAB90A0200002500048B7D@gw.wicourts.gov>
Date: Wed, 27 Jun 2012 11:27:03 -0400
Message-Id: <1340810619-sup-9293@alvh.no-ip.org>
User-Agent: Sup/git
Content-Transfer-Encoding: quoted-printable


Excerpts from Kevin Grittner's message of mi=C3=A9 jun 27 08:40:58 -0400 =
2012:
> Alvaro Herrera  wrote:
> =20
> > here's fklocks v14, which also merges to new master as there were
> > several other conflicts. It passes make installcheck-world now.
> =20
> Recent commits broke it again, so here's a rebased v15.  (No changes
> other than attempting to merge your work with the pg_controldata and
> pg_resetxlog changes and wrapping that FIXME in a comment.)

Oooh, so sorry -- I was supposed to have git-stashed that before
producing the patch.  This change cannot have caused the pg_dumpall
problem below though, because it only touched the multixact cache code.

> Using that patch, pg_upgrade completes, but pg_dumpall fails:

Hmm, something changed enough that requires more than just a code merge.
I'll look into it.

Thanks for the merge.

--=20
=C3=81lvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support