Subject: Re: pg_toast oid limits
To: "David G. Johnston" <david.g.johnston@gmail.com>
References: <A88C1E63-DB62-43C6-B8EC-E78D07574690@ebureau.com>
 <cb232f2c-6b52-8256-d50e-86aaa530c883@commandprompt.com>
 <CAKFQuwbPOhpUjCmnMWuNAyGZ--jp8LdLwJp+ee_hA+2Qx6Q=5A@mail.gmail.com>
Cc: Natalie Wenz <nataliewenz@ebureau.com>,
 pgsql-admin <pgsql-admin@postgresql.org>
From: "Joshua D. Drake" <jd@commandprompt.com>
Organization: Command Prompt, Inc.
Message-ID: <f6409974-a465-2696-d63e-b834a2e36487@commandprompt.com>
Date: Wed, 26 Oct 2016 12:25:29 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: 
 <CAKFQuwbPOhpUjCmnMWuNAyGZ--jp8LdLwJp+ee_hA+2Qx6Q=5A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On 10/26/2016 12:18 PM, David G. Johnston wrote:
> On Wed, Oct 26, 2016 at 12:05 PM, Joshua D. Drake <jd@commandprompt.com

>
> ​While your conclusion about rows/widths may​
>
> ​be accurate I'm missing something if you are correct in stating the above.
>
> Each TOAST table has an associated OID but within that table every VALUE
> (which could mean multiple per record) has an OID and a Sequence Number
> which combined comprise a PK.  Natalie's line of thinking seems to have
> some merit even if I don't know how to answer the question at hand.

Oh that's interesting. I think you are right. That said, the way forward 
I think is still to partition that out and possibly break up the table.

Sincerely,

JD


-- 
Command Prompt, Inc.                  http://the.postgres.company/
                         +1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
Unless otherwise stated, opinions are my own.


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin