"Robert M. Meyer" <rmeyer(at)installs(dot)com> writes:
> Having a bizarre one, today. It seems that when doing a vacuum FULL on
> our system, the backend postgres process gets into a strange state. It
> starts consuming 100% of a cpu (we have two) and is immune to any signal
> (except 9).
Could you attach to the stuck process with a debugger and get a stack
backtrace, so we can get some idea what it's doing? With gdb, the
procedure is
gdb /path/to/postgres-executable
gdb> attach pid-of-process
gdb> bt
gdb> q
regards, tom lane