pgsql-server: For multi-table ANALYZE, use per-table transactions when - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql-server: For multi-table ANALYZE, use per-table transactions when
Date
Msg-id 20040522231438.98F31D1B349@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
For multi-table ANALYZE, use per-table transactions when possible
(ie, when not inside a transaction block), so that we can avoid holding
locks longer than necessary.  Per trouble report from Philip Warner.

Modified Files:
--------------
    pgsql-server/src/backend/access/transam:
        xact.c (r1.166 -> r1.167)

(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/access/transam/xact.c.diff?r1=1.166&r2=1.167)
    pgsql-server/src/backend/commands:
        vacuum.c (r1.276 -> r1.277)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/commands/vacuum.c.diff?r1=1.276&r2=1.277)
    pgsql-server/src/include/access:
        xact.h (r1.62 -> r1.63)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/include/access/xact.h.diff?r1=1.62&r2=1.63)

pgsql-committers by date:

Previous
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql-server: Reduce pg_listener lock taken by NOTIFY et al from
Next
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql-server: Reduce pg_listener lock taken by NOTIFY et al from