Re: What happens when you run out of transaction ID's ???

So ... Any takers ???

"codeWarrior" <GPatnude(at)adelphia(dot)net> wrote in message
news:b0hpc2$pd9$1(at)news(dot)hub(dot)org(dot)(dot)(dot)
> PG 7.2.1
>
> I have a co-programmer working on a separate Web-project that runs against
a
> shared postgreSQL data server... something keeps killing postgreSQL -- I
> believe that he has a nested loop around a BEGIN {transaction} block that
> never issues a COMMIT.... and then END or ROLLBACK...
>
> In the postgreSQL error logs -- (I have been restarting postgres with
> 'pg_ctl restart -D /usr/local/pgsql/data -m smart -l pgdblog.log'.. ) I
have
> occasionally seen transaction ID's up in the 2 million + range -- shortly
> after which the data server crashes... I know about logrotate being the
> preferred method of logging but our Apache installation does NOT have the
> logrotate option (We lease a dedicated server from Pair.com)...
>
> Is this a plausible scenario ??? Is it possible to run postgreSQL into the
> ground by using up all of the transaction ID's ?
>
> ANY help is appreciated....
>
> GP
> Gregory P. Patnude
> 2916 East Upper Hayden Lake Road
> Hayden Lake, ID. 83835
> (208) 762-0762
>
> 1's and 0's are cool. $ A 1 followed by 7-0's.
>
>
>
>