Andrew Dunstan <andrew@dunslane.net> writes:
> further (anecdotal) data point: I have usually seen this after doing a
> number of builds. Rebooting seems to cure the problem (and that's
> happened today agin - I have just seen 2 builds work). Maybe some sort
> of strange shmem corruption?
Hmmm ... that still doesn't make any sense, given that the test is
being run on a freshly started postmaster. Unless it's a hardware
problem? Have you seen this on more than one machine?
regards, tom lane
