| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Radoslav Nedyalkov <rnedyalkov(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_class.oid at 4B |
| Date: | 2021-10-21 05:53:07 |
| Message-ID: | 18daaa4fb24c011b851fa88161c8ac86e335109e.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2021-10-20 at 23:29 +0300, Radoslav Nedyalkov wrote:
> We have a busy database that has oid increasing with 50-100M per month.
> There is no oid type across user attributes anywhere nor user tables with oids;
> Not sure where this generation comes from. If you can hint me, it would be great.
> Also what happens when pg_class.oid reaches 4B.
> pg_class itself is ~40K.
Hard to say, perhaps you are creating lots of temporary tables (watch out
for pg_attribute bloat!). The OID counter will simply wrap around, but there
will be no duplicate OIDs in pg_class.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hubert depesz lubaczewski | 2021-10-21 10:52:53 | Re: Can we get rid of repeated queries from pg_dump? |
| Previous Message | Tom Lane | 2021-10-20 21:46:01 | Re: Can we get rid of repeated queries from pg_dump? |