Re: Re: AW: Re: OID wraparound: summary and proposal - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: Re: AW: Re: OID wraparound: summary and proposal
Date
Msg-id 3B6F6B15.7B423C15@tm.ee
Whole thread Raw
In response to RE: Re: AW: Re: OID wraparound: summary and proposal  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
Responses Re: Re: AW: Re: OID wraparound: summary and proposal
List pgsql-hackers
Tom Lane wrote:
> 
> mlw <markw@mohawksoft.com> writes:
> > Am I being overly simplistic?
> 
> Yes.  For one thing, Relation structs are *not* shared, nor even
> persistent (the relcache will happily discard them). 

Will it be easier to make Relation shared and persistent or creating 
a new shared structure that has just a counter+lock for each 
relation oid ?

> For another, you
> haven't mentioned how we keep the counter up-to-date across system
> restarts.

Perhaps write it to database at checkpoints and get the last INSERTED
record 
from WAL at restart ? 

Probably too simplistic as well ;)


pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: OID wraparound: summary and proposal
Next
From: Matthew Kirkwood
Date:
Subject: Re: Notes about int8 sequences