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

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Jim Hurne <jhurne(at)us(dot)ibm(dot)com>, Michael Lewis <mlewis(at)entrata(dot)com>
Cc: 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-18 14:50:45
Message-ID: a4654733b7ed1c542a95d7dbd8f62c51b94ba8e5.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2020-06-18 15:04:01 Re: ESQL/C no indicator variables ./. error -213
Previous Message Laurenz Albe 2020-06-18 14:47:43 Re: Hiding a GUC from SQL