Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> The other one was reported by Marko Kreen in
> http://archives.postgresql.org/message-id/CACMqXCJjauc9jPa64VxskRN67bYjuYmodz-Mgy-_aoZ6ErG3Yg@mail.gmail.com
> (the thread talks about 2 bugs, but one of them is just pilot error).
> Dimitri posted patches to the real bug for the three affected branches;
> the last one (for master) was in message
> http://archives.postgresql.org/message-id/m2391yy6ub.fsf@2ndQuadrant.fr
> I eyeballed this patch and it seemed to me to fix the problem, but I am
> unfamiliar enough with this dark corner of pg_dump that I can't be sure
> that there aren't bad behaviors being introduced inadvertently.
Yeah, I think that one's on my plate.
regards, tom lane