Re: autovacuum failing on pg_largeobject and disk usage of the pg_largeobject growing unchecked

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jim Hurne" <jhurne(at)us(dot)ibm(dot)com>
Cc: Michael Lewis <mlewis(at)entrata(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: autovacuum failing on pg_largeobject and disk usage of the pg_largeobject growing unchecked
Date: 2020-06-17 18:37:12
Message-ID: 1453694.1592419032@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Jim Hurne" <jhurne(at)us(dot)ibm(dot)com> writes:
> On one of the instances that is exhibiting the "disk leak" behavior, the
> VACUUM ANALYZE VERBOSE command doesn't generate any output or complete
> before I loose the connection to the database (presumably because I hit a
> connection read timeout). Is it possible to configure th read timeout for
> psql?

You could fool with your tcp timeout settings:

https://www.postgresql.org/docs/current/runtime-config-connection.html#RUNTIME-CONFIG-CONNECTION-SETTINGS

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Michel Pelletier 2020-06-17 20:23:19 Hiding a GUC from SQL
Previous Message Jim Hurne 2020-06-17 18:26:24 RE: autovacuum failing on pg_largeobject and disk usage of the pg_largeobject growing unchecked