Search Postgresql Archives

Re: Ever increasing OIDs - gonna run out soon?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Just a quick thought - I know that I don't fully understand tables with oids, and table without oids, is there a link to some more information about why you need oids, or why you don't that I could reference as I'm a bit lost on the subject of oids

Alex.

On 6/12/06, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
Martijn van Oosterhout <kleptog@xxxxxxxxx> 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

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux