On Fri, Nov 21, 2014 at 1:14 AM, Alvaro Herrera
wrote:
>
> If there are foreign keys on the tables, the system internally runs some
> SELECT FOR KEY SHARE queries on the referenced tables (the ones
> containing the primary or unique keys). You can get some multixacts
> that way too.
>
> --
> Álv
Dev Kumkar wrote:
> On Thu, Nov 20, 2014 at 11:15 PM, Alvaro Herrera
> wrote:
> > Merely waiting does not, but more than one lock being acquired on a
> > tuple does cause a multixact to be created. Try SELECT FOR SHARE on two
> > transactions on the same tuple.
>
> Sure.
> Also what if there are
On Thu, Nov 20, 2014 at 11:15 PM, Alvaro Herrera
wrote:
> Search for "burnmulti" in the archives, which is a contrib module to
> test pg_multixact.
>
Thanks, got some links. Will give a try and get back.
Merely waiting does not, but more than one lock being acquired on a
> tuple does cause a mu
Dev Kumkar wrote:
> Hellos,
>
> How to manually increase pg_multixact members and offsets?
Search for "burnmulti" in the archives, which is a contrib module to
test pg_multixact.
> Does a transaction waiting for exclusive lock or shared lock result into
> entry being created in pg_multixact?
Me
