Re: pg_restore encounter deadlock since PostgreSQL bringing up

Hi,
Per my understanding, From the query which resulted in the deadlock
“SELECT sequence_name, start_value, increment_by***********”, it appears
that the query which holds the lock is related to sequence numbers. From our
understanding it appears that, whenever there is a serial type of data
member, PostgreSQL internally needs to keep track of sequence numbers across
the dump and restore. Is it possible select query is triggered by PostgreSQL
bringing up(to bring up internal database) instead of dump file? because
from the log, it looks failed while doing DROP SCHEMA public CASCADE.

--
View this message in context: http://postgresql.nabble.com/pg-restore-encounter-deadlock-since-PostgreSQL-bringing-up-tp5874146p5874160.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.