Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hufyO-0001vU-NY for pgsql-admin@arkaria.postgresql.org; Mon, 05 Aug 2019 16:36:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hufyN-0003rW-Iu for pgsql-admin@arkaria.postgresql.org; Mon, 05 Aug 2019 16:36:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hufyN-0003pI-85 for pgsql-admin@lists.postgresql.org; Mon, 05 Aug 2019 16:36:35 +0000 Received: from mail-oi1-x22a.google.com ([2607:f8b0:4864:20::22a]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hufyL-0007u4-3s for pgsql-admin@lists.postgresql.org; Mon, 05 Aug 2019 16:36:34 +0000 Received: by mail-oi1-x22a.google.com with SMTP id 65so62472882oid.13 for ; Mon, 05 Aug 2019 09:36:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=jM3M1/4Ouc8QcVWkz0L5pR2ObZgfrr1C0So2OpL3Euw=; b=Sqj481GrD8V87mVlYQXDVcZd61LNbX3TEqr3tqIOJLlp710Gu0szjNQo54plV7FNXC Dq5w8HGOsOxL0S8umN817dvBfxolh9mQ7N9VCo83D6i7HLYAnOXuQGMdq9TFj5iQrx3j k7pEnTzDubCaM70j4/8AWbd7LKWo9OhBya/+K2p2f7HKXLQZl/epR9OivXS/H84W34Ys 8AYhEWEesUbwFyKS2FCmzQtPfVCPuussq8mA/N/cOjQ0Nyatlm8uMwFhRv4di9jFVo0T h15u2XfEwgnf7ORsZh79y2JTlvWZhQ2wNPt5FNEkwiZLibiEJOonBw/2N51qqPcokoge +eZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=jM3M1/4Ouc8QcVWkz0L5pR2ObZgfrr1C0So2OpL3Euw=; b=ZsS7N2DogecQ2tkDuUfNa0Vp1VrjffyO0j8RmULuIWGJnXptS1hoq5bX5rCp3m9btU SapmAmc7hghGqeeTX+jfG5ICN8uQAWXI/ykgUKIo3KG574YoNXSDHkkrZERX3GIWc9Pw 0IskgzG+ZL1Va5jtkSXaswF34FVgsSgrhx8wZQA9xVWzsJPPX3tybFRUndUY6l07OBL0 ghphqC1KqSl1FNtNvFaR+0+H0EvXbLC51D1mSYku3QsaPfR079IS4RLvFzNFJX6b/Hm7 qms9pU3xj5/awUhR8msyL9V2yOJvnvQW5r+bjA1q2vKcoPsZmrNEKBpU1clNhb91WExc TFPA== X-Gm-Message-State: APjAAAVaVA89jWxah5Ys/wh4cOjl3tw3wpH+Y0mnYzwTOI/zbRSdrLo9 6O46frEfSpUfOjL0neydYJnIxVyZPlX4Bw== X-Google-Smtp-Source: APXvYqxlmgGWsP4Fgm+WrEx05Fg1hDhis0RLwUcw3t3T7wPuEWmb2MV8vxSYlVE/B3uFQIEARgBPbg== X-Received: by 2002:aca:c084:: with SMTP id q126mr11457869oif.124.1565022989953; Mon, 05 Aug 2019 09:36:29 -0700 (PDT) Received: from [192.168.1.10] (ip70-171-116-89.no.no.cox.net. [70.171.116.89]) by smtp.googlemail.com with ESMTPSA id b138sm28847718oii.7.2019.08.05.09.36.28 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Aug 2019 09:36:28 -0700 (PDT) Subject: Re: Diagnosing a massive toast file To: pgsql-admin@lists.postgresql.org References: From: Ron Message-ID: <3da6ffe8-28ef-fb9a-e6e8-1f0d243cc8e9@gmail.com> Date: Mon, 5 Aug 2019 11:36:27 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------D0CF83721208E02237EDEC6E" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------D0CF83721208E02237EDEC6E Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit On 8/5/19 11:32 AM, Wells Oliver wrote: > Hi all, I have not seen this before, but one our toast tables has gotten > to 15GB, the biggest table in the DB. I don't know why, is there some way > I can diagnose what's causing this? > >  I don't think I've ever seen a toast table even half of this size, so > it's concerning. We've got *lots* of toast tables that big.  Are you asking how to find the "human readable name" associated with the toast table? And have you vacuumed it lately? -- Angular momentum makes the world go 'round. --------------D0CF83721208E02237EDEC6E Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit On 8/5/19 11:32 AM, Wells Oliver wrote:
Hi all, I have not seen this before, but one our toast tables has gotten to 15GB, the biggest table in the DB. I don't know why, is there some way I can diagnose what's causing this?

 I don't think I've ever seen a toast table even half of this size, so it's concerning.

We've got lots of toast tables that big.  Are you asking how to find the "human readable name" associated with the toast table?

And have you vacuumed it lately?

--
Angular momentum makes the world go 'round.
--------------D0CF83721208E02237EDEC6E--