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

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: codeWarrior <gpatnude(at)hotmail(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: What happens when you run out of transaction ID's ???
Date: 2003-01-29 06:20:13
Message-ID: 20030128221617.W4312-100000@megazone23.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Tue, 21 Jan 2003, codeWarrior wrote:

> So ... Any takers ???

I don't think anyone saw the original, or at least I never received the
quoted message.

> "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

million or billion? You should be fine up until you're in the billions.
At which point I think you need to vacuum everything.

Does the log show anything around the time it shuts down that might give a
hint?

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-01-29 06:30:19 Re: ERROR: ExecEvalAggref
Previous Message Shridhar Daithankar<shridhar_daithankar@persistent.co.in> 2003-01-29 06:14:13 Re: Using RSYNC for replication?