From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Souquieres Adam <adam(dot)souquieres(at)axege(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: 8.4 -> 9.1 : ANALYSE VERBOSE; -> out of shared memory |
Date: | 2014-05-12 14:24:16 |
Message-ID: | 21659.1399904656@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Souquieres Adam <adam(dot)souquieres(at)axege(dot)com> writes:
> When i relaunch my ANALYSE VERBOSE, pg_locks table grows quickly from 20
> lines to more than 1000 lines and still growing, all the lines are owned
> by the same "virtual transaction" and the same "pid".
Hm. I experimented a bit and looked at the code, and I find I was not
remembering ANALYZE's behavior exactly right: it only processes all the
tables inside one transaction if you start it inside a transaction block
(ie, after BEGIN, or inside a function). If you just run it by itself
then it does a transaction per table, just like VACUUM. So I'm thinking
there's something you're not telling us about exactly how you invoke
ANALYZE.
> When i finish to write this email, i juste hit more than 3200 lock owned
> by the same transaction !
Could you show us some of those locks (a few dozen lines from pg_locks)?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Souquieres Adam | 2014-05-12 14:49:38 | Re: 8.4 -> 9.1 : ANALYSE VERBOSE; -> out of shared memory |
Previous Message | Souquieres Adam | 2014-05-12 14:05:23 | Re: 8.4 -> 9.1 : ANALYSE VERBOSE; -> out of shared memory |