| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | John Sidney-Woollett <johnsw(at)wardbrook(dot)com>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Ever increasing OIDs - gonna run out soon? |
| Date: | 2006-06-12 18:04:27 |
| Message-ID: | 11059.1150135467@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> Well, you have to be using a lot of OIDs for this to be an issue. At
> your stated rate of 1.5 million OIDs per day it will take just under
> eight years before you wraparound. That's a lot of OIDs and most
> databases don't get anywhere near that many, which is why it's not a
> big deal for most people...
It should also be pointed out that OID wraparound is not a fatal
condition. Pre-8.1 you might get occasional query failures due to
trying to insert duplicate OIDs, but that's about it.
> This gives you a list of tables that use OIDs. Maybe it can help you
> track down the problem.
Look at pg_class.relhasoids --- easier, and more reliable.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Sidney-Woollett | 2006-06-12 19:05:05 | Re: Ever increasing OIDs - gonna run out soon? |
| Previous Message | Florian Weimer | 2006-06-12 17:55:22 | Re: Disk corruption detection |