| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Natalie Wenz <nataliewenz(at)ebureau(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: pg_toast oid limits |
| Date: | 2016-10-26 19:25:29 |
| Message-ID: | f6409974-a465-2696-d63e-b834a2e36487@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-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(at)commandprompt(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Poul Kristensen | 2016-10-26 21:23:38 | Re: PostgresSQL 9.5 and systemd autorestart but without replication. |
| Previous Message | Tom Lane | 2016-10-26 19:22:57 | Re: pg_toast oid limits |