pg_toast oid limits

From: Natalie Wenz <nataliewenz(at)ebureau(dot)com>
To: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: pg_toast oid limits
Date: 2016-10-26 18:58:29
Message-ID: A88C1E63-DB62-43C6-B8EC-E78D07574690@ebureau.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi all,

I am seeing some performance issues that I'm trying to track down on a large database. One of the things I'm beginning to suspect is a particularly large table with many columns, about 200 of which (type text) contain large chunks of data. Now, for a given row, maybe 10-30 of those columns contain data, so not all 200 for each row, but the data can still be pretty sizable. There are currently around 750 million records in this table (and is about 22TB in size). I was trying to learn more about toast, and I see some references in the wiki and the hackers list to performance issues when you approach the 4 billion oids for a single table (which, I gather, are used when the data is toasted). Given my rudimentary understanding of how the whole toast thing works, I was wondering if there is a way to see how many oids are used for a table, or another way to know if we're running into toast limits for a single table.

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.

Many thanks!
Natalie

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Joshua D. Drake 2016-10-26 19:05:33 Re: pg_toast oid limits
Previous Message Tom Lane 2016-10-26 15:49:47 Re: PostgresSQL 9.5 and systemd autorestart but without replication.