Alvaro Herrera wrote:
> 3. the bgwriter is seen writing WAL entries at checkpoint. At shutdown,
> this might cause an error to be reported on how there was not supposed
> to be activity on the log. I didn't save the exact error report and I
> can't find it in the source :-(
LOG: received fast shutdown request
LOG: aborting any active transactions
FATAL: terminating connection due to administrator command
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: INSERT @ 0/67F05F0: prev 0/67F05C0; xid 0: Heap2 - hintbits: rel 1663/16384/1259; blk 4
CONTEXT: writing block 4 of relation 1663/16384/1259
LOG: xlog flush request 0/67F06C0; write 0/0; flush 0/0
CONTEXT: writing block 4 of relation 1663/16384/1259
LOG: INSERT @ 0/67F06C0: prev 0/67F05F0; xid 0: Heap2 - hintbits: rel 1663/16384/2608; blk 40
CONTEXT: writing block 40 of relation 1663/16384/2608
LOG: xlog flush request 0/67F0708; write 0/67F06C0; flush 0/67F06C0
CONTEXT: writing block 40 of relation 1663/16384/2608
LOG: INSERT @ 0/67F0708: prev 0/67F06C0; xid 0: Heap2 - hintbits: rel 1663/16384/1249; blk 29
CONTEXT: writing block 29 of relation 1663/16384/1249
LOG: xlog flush request 0/67F0808; write 0/67F0708; flush 0/67F0708
CONTEXT: writing block 29 of relation 1663/16384/1249
LOG: INSERT @ 0/67F0808: prev 0/67F0708; xid 0: XLOG - checkpoint: redo 0/67F05F0; tli 1; xid 0/9093; oid 90132; multi
1;offset 0; shutdown
LOG: xlog flush request 0/67F0850; write 0/67F0808; flush 0/67F0808
PANIC: concurrent transaction log activity while database system is shutting down
LOG: background writer process (PID 17411) was terminated by signal 6: Aborted
I am completely at a loss what to do here.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.