Doug McNaught <doug@wireboard.com> writes:
> It's possible that the client drivers you're using weren't updated to
> reflect the unlimited tuple size in 7.1.
No; the error he's quoting is an internal backend failure, so it's
not a client-side problem. It looks to me like TOAST is failing to
get the job done on compacting an oversize tuple, which is why I wanted
to know more about the table in question.
regards, tom lane
