From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | pinker <pinker(at)onet(dot)eu>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_am access in simple transaction? |
Date: | 2016-11-25 14:54:48 |
Message-ID: | 243dfa28-8d2f-b825-685d-a00f303879f7@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/25/2016 04:40 AM, pinker wrote:
> Hi,
> I'm doing simple tests with lsof on data catalog with bash script:
>
> #!/bin/bash
> for i in {0..2000}
> do
> psql -U postgres -c '*BEGIN; select pg_sleep(30); COMMIT*'&
> done
>
> and i measure number of open files and what files are affected by specific
> command.
> Lsof has shown me that the only file that was open during this test was:
> data/base/13328/2601, which is pg_catalog table pg_am.
>
> Why postgres opens a table that stores information about relation (index)
> access methods, while none index evidently is in use?
I can not replicate using 50 clients instead of 2000. I suspect either
has to do with the extreme number of clients or it is an artifact of
from some other process.
>
>
>
>
>
>
>
>
> --
> View this message in context: http://postgresql.nabble.com/pg-am-access-in-simple-transaction-tp5931974.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2016-11-25 15:01:04 | Re: query locks up when run concurrently |
Previous Message | Simon Riggs | 2016-11-25 14:52:30 | Re: Replicating hundreds of thousandw of rows |