| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(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:18:22 |
| Message-ID: | CAKFQuwbPOhpUjCmnMWuNAyGZ--jp8LdLwJp+ee_hA+2Qx6Q=5A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, Oct 26, 2016 at 12:05 PM, Joshua D. Drake <jd(at)commandprompt(dot)com>
wrote:
> On 10/26/2016 11:58 AM, Natalie Wenz wrote:
>
>>
>> What I was reading, for reference:
>> https://wiki.postgresql.org/wiki/TOAST
>> http://osdir.com/ml/postgresql-pgsql-hackers/2015-01/msg01901.html
>>
>> Also, we are running postgres 9.5.4.
>>
>
> oids are used per relation not per row.
>
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.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-10-26 19:22:57 | Re: pg_toast oid limits |
| Previous Message | Joshua D. Drake | 2016-10-26 19:05:33 | Re: pg_toast oid limits |