Re: strange locks on PG 11 with Golang programs
От
Josef Machytka
Тема
Re: strange locks on PG 11 with Golang programs
Дата
Msg-id
CAGvVEFuPfVYLKJq=uzB_eLXfOwAjrM09HtVO5G6+6XcHi3hukQ@mail.gmail.com
Ответ на
Re: strange locks on PG 11 with Golang programs (Julien Rouhaud)
Список
Дерево обсуждения
strange locks on PG 11 with Golang programs Josef Machytka <josef.machytka@gmail.com>
Re: strange locks on PG 11 with Golang programs Julien Rouhaud <rjuju123@gmail.com>
Re: strange locks on PG 11 with Golang programs Josef Machytka <josef.machytka@gmail.com>
Re: strange locks on PG 11 with Golang programs Julien Rouhaud <rjuju123@gmail.com>
Re: strange locks on PG 11 with Golang programs Achilleas Mantzios <achill@matrix.gatewaynet.com>
Re: strange locks on PG 11 with Golang programs "Peter J. Holzer" <hjp-pgsql@hjp.at>
On Mon, 9 Mar 2020 at 09:58, Julien Rouhaud <rjuju123@gmail.com> wrote:
The query displayed is just the query currently executing, but if the
connection is in a transaction the problematic lock could have been acquired by
any previously executed query. Did you check in pg_stat_activity if the
connection is in a transaction (e.g. query_start != xact_start)?
Oh, I see. Thank you. I modified query from wiki and it shows that blocking session actually runs for ~12 hours already. Only last COPY command started recently. So maybe golang library did not close session properly and reused it in another completely different task? Although I defer db.Close() everywhere...
В списке pgsql-general по дате отправления
