Postgres Pro
Downloads
Home   >   mailing lists

Re: We should lazy-initialize the deadlock checker state memory - Mailing list pgsql-hackers

From Tom Lane
Subject Re: We should lazy-initialize the deadlock checker state memory
Date
Msg-id 1347009.1749168090@sss.pgh.pa.us
Whole thread Raw
In response to We should lazy-initialize the deadlock checker state memory  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Tree view 
Andres Freund <andres@anarazel.de> writes:
> ISTM that we could move the call to InitDeadLockChecking() to the start of
> CheckDeadLock(), before it acquires all the locks. That'd require making it
> safe to call InitDeadLockChecking() multiple times, but that's obviously
> trivial.

Hmph.  Do we even need that to be persistent storage at all, rather
than just allocating it for the duration of CheckDeadLock?

            regards, tom lane

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: We should lazy-initialize the deadlock checker state memory
Next
From: Andres Freund
Date:
Subject: Re: Retiring some encodings?