Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1f0U80-0001Tj-6e
	for pgsql-admin@arkaria.postgresql.org; Mon, 26 Mar 2018 15:33:44 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1f0U7y-0001sp-Od
	for pgsql-admin@arkaria.postgresql.org; Mon, 26 Mar 2018 15:33:42 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <depesz@depesz.com>)
	id 1f0U7y-0001sf-Ds
	for pgsql-admin@lists.postgresql.org; Mon, 26 Mar 2018 15:33:42 +0000
Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com)
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <depesz@depesz.com>)
	id 1f0U7w-0001cC-4q
	for pgsql-admin@postgresql.org; Mon, 26 Mar 2018 15:33:41 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=depesz.com;
 s=20170201;
	h=In-Reply-To:Content-Type:MIME-Version:References:Reply-To:Message-ID:Subject:Cc:To:Sender:From:Date;
 bh=20HTeMYmfXI+8ZOD8TdTVwSj8TGBp07t7IRR20+C3oM=;
	b=etjb12WGpqFK+Mn/oMo0b/kcJyhwnfsd7l5GQXdFPpHOR8lRdDy++5oi8tKYB6gt5g+3ur3x1TdvwchiS06CkmqvTYHWqdbobxWDcyVXTPqnMPlYmpkMcjTIKtAQkBAQ1WuthOSHjYDsVUVP2jEgYnfLFEVa+wERUSCitMwu/yg=;
Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com)
	by depesz.com with esmtpa (Exim 4.84_2)
	(envelope-from <depesz@depesz.com>)
	id 1f0U7t-0002Yo-Nl; Mon, 26 Mar 2018 17:33:37 +0200
Date: Mon, 26 Mar 2018 17:33:37 +0200
From: hubert depesz lubaczewski <depesz@depesz.com>
Sender: depesz@depesz.com
To: Artem Tomyuk <admin@leboutique.com>
Cc: Keith <keith@keithf4.com>, pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: how to shrink pg_attribute table in some database
Message-ID: <20180326153337.GA8484@depesz.com>
Reply-To: depesz@depesz.com
References: 
 <CANYYVqKwgR8TK6ar54vbXLc01KH-_ppM=qh6GLQ6edmmexX-EQ@mail.gmail.com>
 <CAHw75vuFvy_Tn9ZT0zANugeJOLhrfcmxv4r+XeJV0NszVNmn5Q@mail.gmail.com>
 <CANYYVqLSEdHVzXiUUHp+mPM+X5tbbP_oOfHh5-RJGoTkReGsmA@mail.gmail.com>
 <20180326141756.GB708@depesz.com>
 <CANYYVq+5Og_e=d4h4uvuh3s-e1PfdR5t1QeStPKoR24q_DdZfw@mail.gmail.com>
 <20180326152425.GA23643@depesz.com>
 <CANYYVqJn8pxN-YU4C7Y=u1nxrqzmWwwz4bXLFs6_JbQwpiTggA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: 
 <CANYYVqJn8pxN-YU4C7Y=u1nxrqzmWwwz4bXLFs6_JbQwpiTggA@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Precedence: bulk

On Mon, Mar 26, 2018 at 06:32:25PM +0300, Artem Tomyuk wrote:
> Thanks,
> 
> as we understand there is a lack of autovacuum max workers in
> postgresql.conf.

that is a contributing factor. but the sheer size of this table means
that something is doing something very bad in your application.

> 
> One question more, what impact would be on streaming replication? Will full
> vacuum create extra wal files during full vacuum?

Yes it will - in the size of new table.

Best regards,

depesz