On 2020-03-09 11:02:37 +0200, Achilleas Mantzios wrote:
> Fully review your programs for connection / xaction leaks. Do you use a
> connection pool?
Go's sql package encourages the use of connection pools (type DB) over
single connections (type Conn):
| Prefer running queries from DB unless there
On Mon, Mar 09, 2020 at 10:21:23AM +0100, Josef Machytka wrote:
> On Mon, 9 Mar 2020 at 09:58, Julien Rouhaud 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 previousl
On Mon, 9 Mar 2020 at 09:58, Julien Rouhaud 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 i
On 9/3/20 10:51 π.μ., Josef Machytka wrote:
We are lately experiencing very strange locks on PostgreSQL 11.7 when we
process ETL tasks using our programs in Go 1.13.8 using standard libraries sql
and pq.
ETL task has to rename tables but PostgreSQL shows that this simple operation waits for L
On Mon, Mar 09, 2020 at 09:51:21AM +0100, Josef Machytka wrote:
> We are lately experiencing very strange locks on PostgreSQL 11.7 when we
> process ETL tasks using our programs in Go 1.13.8 using standard libraries
> sql and pq.
>
> ETL task has to rename tables but PostgreSQL shows that this simp
