Thanks to visit codestin.com
Credit goes to postgrespro.com

Request a Demo
Home   >   mailing lists

Re: shared memory release following failed lock acquirement. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: shared memory release following failed lock acquirement.
Date
Msg-id [email protected]
Whole thread Raw
In response to Re: shared memory release following failed lock acquirement.  ("Simon Riggs" <[email protected]>)
Responses Re: shared memory release following failed lock acquirement.
List pgsql-hackers
Tree view 
"Simon Riggs" <[email protected]> writes:
> Does this mean that the parameter max_locks_per_transaction isn't honoured
> at all, it is just used to size the lock table

Yes, and that's how it's documented.
        regards, tom lane

pgsql-hackers by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: shared memory release following failed lock acquirement.
Next
From: Neil Conway
Date:
Subject: Re: tweaking MemSet() performance - 7.4.5