zh1029 writes:
> Unfortunately what's the process 2720 is unknown as no any else log to
> indicate it. It might because the debug level of PostgreSQL had been set too
> lower to show more.
The query you quoted for 2720 looks exactly like one that pg_dump will
issue, cf dumpSequence(). What I thi
zh1029 wrote:
> While start PostgreSQL(9.3.6) and execute pg_restore soon after PostgreSQL
> bringing up. I encounter pg_restore failure because of deadlock detected.
pg_restore will not deadlock with itself or system startup.
Set log_connections to "on", then you will see who connected and
cause
On 11/16/2015 10:55 PM, zh1029 wrote:
Unfortunately what's the process 2720 is unknown as no any else log to
indicate it. It might because the debug level of PostgreSQL had been set too
lower to show more.
if its a linux system, try...
ps uww -p 2720
logged on as root, and it should show
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
mem
Unfortunately what's the process 2720 is unknown as no any else log to
indicate it. It might because the debug level of PostgreSQL had been set too
lower to show more.
--
View this message in context:
http://postgresql.nabble.com/pg-restore-encounter-deadlock-since-PostgreSQL-bringing-up-tp5874
Hi,
pg_restore is executed by our own process actually, before that, our
process connects the data base via ODBC to access database template1 see if
PostgreSQL server is up. But pg_restore still failed after connect database
I understand the result is same as pg_ctrl output, is that true? Thank
On 11/16/2015 08:24 PM, zh1029 wrote:
Hi,
While start PostgreSQL(9.3.6) and execute pg_restore soon after PostgreSQL
bringing up. I encounter pg_restore failure because of deadlock detected.
postgres[2737]: [3-1] LOG: process 2737 detected deadlock while waiting for
AccessExclusiveLock on rela
On Tue, Nov 17, 2015 at 3:24 PM, zh1029 wrote:
> Hi,
>
> While start PostgreSQL(9.3.6) and execute pg_restore soon after PostgreSQL
> bringing up. I encounter pg_restore failure because of deadlock detected.
>
> postgres[2737]: [3-1] LOG: process 2737 detected deadlock while waiting
> for
> Acce
Hi,
While start PostgreSQL(9.3.6) and execute pg_restore soon after PostgreSQL
bringing up. I encounter pg_restore failure because of deadlock detected.
postgres[2737]: [3-1] LOG: process 2737 detected deadlock while waiting for
AccessExclusiveLock on relation 7 of database 24577 after 1000.
