Re: autovacuum failing on pg_largeobject and disk usage of thepg_largeobject growing unchecked - Mailing list pgsql-general

From Laurenz Albe
Subject Re: autovacuum failing on pg_largeobject and disk usage of thepg_largeobject growing unchecked
Date
Msg-id a4654733b7ed1c542a95d7dbd8f62c51b94ba8e5.camel@cybertec.at
Whole thread Raw
In response to RE: autovacuum failing on pg_largeobject and disk usage of thepg_largeobject growing unchecked  ("Jim Hurne" <jhurne@us.ibm.com>)
List pgsql-general
On Wed, 2020-06-17 at 14:26 -0400, Jim Hurne wrote:
> 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?

I have never heard about a connection read timeout for "psql".

I'd look into the server log; perhaps there is an error that indicates
data curruption that crashes the server?

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com




pgsql-general by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Hiding a GUC from SQL
Next
From: Tom Lane
Date:
Subject: Re: ESQL/C no indicator variables ./. error -213