pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: Natalie Wenz <nataliewenz@ebureau.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: pg_toast oid limits
Date: Wed, 26 Oct 2016 12:25:29 -0700
Message-ID: <f6409974-a465-2696-d63e-b834a2e36487@commandprompt.com> (raw)
In-Reply-To: <CAKFQuwbPOhpUjCmnMWuNAyGZ--jp8LdLwJp+ee_hA+2Qx6Q=5A@mail.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>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

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



view thread (7+ messages)  latest in thread

Message-ID: <f6409974-a465-2696-d63e-b834a2e36487@commandprompt.com>
Permalink:  ../f6409974-a465-2696-d63e-b834a2e36487@commandprompt.com/
Also on:    postgresql.org/message-id/f6409974-a465-2696-d63e-b834a2e36487@commandprompt.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: jd@commandprompt.com, david.g.johnston@gmail.com, nataliewenz@ebureau.com
  Subject: Re: pg_toast oid limits
  In-Reply-To: <f6409974-a465-2696-d63e-b834a2e36487@commandprompt.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox