Brian Hurt <bhurt(at)janestcapital(dot)com> writes:
> Execute, on a fresh database, the following sql, to recreate the bug:
Hmm, I thought that stack trace looked a bit familiar --- we seem to
have fixed the problem as of 8.2. Unfortunately I can't recall what
the relevant change was exactly; time for some digging in the CVS logs.
regards, tom lane