> > select recordid from t1 where oid = $lastoid; > > Because the last select could return several lines. > > Shouldn't! oids are unique over the whole database server (I'm right on > this?) So you should have only one or non. Well, no, that's the point of this whole discussion. If you give it enough time, oids can wrap around, which apparently doesn't affect the functionning of the database but application that depend on unique oids could get hosed. Yes, the documentation is wrong. Florent
- [GENERAL] Re: is PG able to handle a >500 GB Database... Florent Guillaume
- [GENERAL] Re: is PG able to handle a >500 GB Dat... Florent Guillaume
- [GENERAL] Re: is PG able to handle a >500 GB... Martin A. Marques
- [GENERAL] Re: is PG able to handle a >50... Florent Guillaume
- [GENERAL] Re: is PG able to handle a &g... Martin A. Marques
- [GENERAL] Re: is PG able to handle... Florent Guillaume
- Re: [GENERAL] Re: is PG able t... Tom Lane
- Re: [GENERAL] Re: is PG ab... Florent Guillaume
- Re: [GENERAL] Re: is PG ab... Bruce Momjian
- [GENERAL] OID/XID allocati... Tom Lane
- [GENERAL] Re: OID/XID allo... Bruce Momjian
- Re: [GENERAL] OID/XID allo... Bruce Momjian