Adam Haberlach <adam(at)newsnipple(dot)com> writes:
> Whenever a query requiring an aggregate is attempted, it spits out:
> cannot open pg_aggregate: No such file or directory
> and fails.
Weird. It would be useful to find out exactly what pathname it's trying
to open. strace'ing the backend might be the easiest way.
> Does anyone know if there could be an issue between the i686 and
> athlon optimizations?
Seems unlikely that it would manifest this way, if so. The error is
coming from a low-level routine that would also be used for opening
any other table ...
regards, tom lane