My guess it's a spinlock, probably xlogctl->info_lck via RecoveryInProgress(). Unfortunately inline assembler doesn't always seem to show up correctly in profiles...
What worked for me was to build with -fno-omit-frame-pointer - that normally shows the callers, even if it can't generate a proper symbol name.
Soni: Do you use Hot Standby? Are there connections active while you have that problem? Any other processes with high cpu load?
Greetings,
Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
It is
96.62% postgres [.] StandbyReleaseLocks
as Jeff said. It runs quite long time, more than 5 minutes i think
i also use hot standby. we have 4 streaming replica, some of them has active connection some has not. this issue has last more than 4 days. On one of the standby, above postgres process is the only process that consume high cpu load.