Re: [gnue-geas] Re: Proposal: [HACKERS] OID wraparound: summary and proposal

2001-08-14 Thread Reinhard Mueller
Neil Tiffin wrote: > I have not even considered multiple database servers running different > database, which is our design goal. In this case we would like to have > a slimmed down (and blazingly fast) PostgreSQL server in which we manage > the uid in our middleware. This is because the uid

Re: Proposal: [HACKERS] OID wraparound: summary and proposal

2001-08-07 Thread Neil Tiffin
At 11:22 AM -0400 8/7/01, Tom Lane wrote: >Neil Tiffin <[EMAIL PROTECTED]> writes: >> I have not even considered multiple database servers running >> different database, which is our design goal. In this case we would >> like to have a slimmed down (and blazingly fast) PostgreSQL server in >>

Re: Proposal: [HACKERS] OID wraparound: summary and proposal

2001-08-07 Thread Tom Lane
Neil Tiffin <[EMAIL PROTECTED]> writes: > I have not even considered multiple database servers running > different database, which is our design goal. In this case we would > like to have a slimmed down (and blazingly fast) PostgreSQL server in > which we manage the uid in our middleware. Thi

Re: Proposal: [HACKERS] OID wraparound: summary and proposal

2001-08-07 Thread Neil Tiffin
At 10:09 AM +0500 8/7/01, Hannu Krosing wrote: >Neil Tiffin wrote: >> >> I would just like to comment that for our project, GNU Enterprise, we >> use our own 128 bit object ID that is unique (UUID) for every row in >> all tables. >> >> It seems to me, without having looked into it, that having

Re: Proposal: [HACKERS] OID wraparound: summary and proposal

2001-08-07 Thread Hannu Krosing
Neil Tiffin wrote: > > I would just like to comment that for our project, GNU Enterprise, we > use our own 128 bit object ID that is unique (UUID) for every row in > all tables. > > It seems to me, without having looked into it, that having both a > PostgreSQL UID and our own 128 bit objectid (

Re: Proposal: [HACKERS] OID wraparound: summary and proposal

2001-08-03 Thread Neil Tiffin
I would just like to comment that for our project, GNU Enterprise, we use our own 128 bit object ID that is unique (UUID) for every row in all tables. It seems to me, without having looked into it, that having both a PostgreSQL UID and our own 128 bit objectid (UUID) is redundant and slows t

Proposal: [HACKERS] OID wraparound: summary and proposal

2001-08-03 Thread Zeugswetter Andreas SB
> > At the same time that we announce support for optional OIDs, > > we should announce that, in future releases, OIDs will only be > > guaranteed unique (modulo wraparounds) within a single table. ... if an appropriate unique constraint is explicitly created. > > Seems reasonable --- that wi