| From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Cc: | "Morris Goldstein" <morrigold(at)gmail(dot)com> |
| Subject: | Re: Transaction id wraparound problem |
| Date: | 2006-11-16 00:13:08 |
| Message-ID: | 200611151713.08428.pgsql@bluepolka.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wednesday November 15 2006 4:18 pm, Morris Goldstein wrote:
> If I'm vacuuming every day (or two), and not running anywhere
> near 1 billion transactions a day, why am I running into
> transaction id wraparound problems?
> Is this just complaining that template0 and template1 haven't
> been vacuumed in the over 2 billion transactions encountered
> by testdb? (I never touch template0 and template1.) If that's
> what's going on, I take it that I have no risk of data loss?
> And is there some reason to vacuum these databases, (other
> than to avoid the scary messages)?
I don't believe template0 ever gets vacuumed since it doesn't
allow connections. Template1 can take a "vacuum" command, and I
think that might be where your message is coming from. If you
vacuum it, do your messages go away? Your testdb looks like it
was vacuumed about 10,000 transactions ago.
Ed
| From | Date | Subject | |
|---|---|---|---|
| Next Message | surabhi.ahuja | 2006-11-16 05:17:08 | Re: empty folder for downlaoding PostgreSQL 8.1.5 for FC4 |
| Previous Message | Chris Mulcahy | 2006-11-15 23:53:02 | Re: ORDER BY |