--- In firebird-support@yahoogroups.com, "Alan McDonald" <alan@...> wrote:

>
> > > > Hi
> > > > i need to know if this limitation exists or not.
> > > > transaction enumeration in Firebird is max integer or unsigned
> integer?
> > > > and what happens when i reach 2^31=2147483648 transaction ID or if
> > > > is unsigned 2^32=4294967296 i read somewhere that in FB1.5 this
> > > > corrupt database - what about with 2.1.4 and new FB2.5, FB3.0?
> > > > Karol Bieniaszewski
> > > >
> > >
> > > In 32 bit positive range, at a rate of 1 transaction per 30 seconds
> > > average. That's 2,108 years between backup and restore cycles
> > >
> > > Alan
> > >
> >
> > Hi Alan,
> >
> > then you confirm that this limitation exists?
> > I yes i am in bad situation
> > because now i have ~18 000 000 transaction per day this is ~200
> transaction
> > per second :/
> >
> > I see that i need to take off line my database after <4 month :/ This
> counter
> > not restart self?
> > I really need to backup and restore cycle?
> >
> > Karol Bieniaszewski
>
> Anyway not sure if it's 64bit transaction IDs in the 64 bit version.
> That would extend your transaction range to a life 9,000 billion years at 1
> per 30 secs
> Or 200 per second = 1.5 billion years between BR cycles
>
> What sort of hardware is providing you with 200 transactions pe second? I
> would have thought you'd hit a brick wall way before this.
>
> Alan
>

I see a light in the tunnel:)
But does anyone confirm? 64-bit transaction ID on 64-bit Firebird?


Karol Bieniaszewski