Skip site navigation (1) Skip section navigation (2)

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

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql-server: For multi-table ANALYZE, use per-table transactions when
Date: 2004-05-22 23:14:38
Message-ID: 20040522231438.98F31D1B349@svr1.postgresql.org (view raw or flat)
Thread:
Lists: 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

Next:From: Tom LaneDate: 2004-05-23 03:50:45
Subject: pgsql-server: Handle impending sinval queue overflow by means of a
Previous:From: Tom LaneDate: 2004-05-22 21:58:41
Subject: pgsql-server: Reduce pg_listener lock taken by NOTIFY et al from

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group