Re: apparent wraparound

From: Reece Hart <reece(at)harts(dot)net>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: apparent wraparound
Date: 2006-07-14 19:30:48
Message-ID: 1152905448.5106.330.camel@tallac.gene.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> I'd ask you the same question I asked Thomas: do you continue to get those log messages
> during subsequent checkpoints?

No, I don't. The error did not reappear during ~2h of continuous
inserts since my report, didn't reappear after a forced checkpoint
(i.e., via psql), and did not reappear on a recent stop/start cycle.

There was a period when my cron-driven vacuuming was broken and, in
principle, I might have been susceptible to wraparound. However, I
don't see how we could have had 1B transactions in that period.

One other tidbit: a colleague inadvertently updated ~10M records. After
this, I started getting errors like:
number of page slots needed (2952496) exceeds max_fsm_pages (500000)
I restored from a backup, but still have:
'number of page slots needed (183248) exceeds max_fsm_pages (50000)'
(I reduced max_fsm_pages after the restore.)

I'm not sure whether the vacuum and fsm info is relevant.

-Reece

--
Reece Hart, http://harts.net/reece/, GPG:0x25EC91A0

Responses

Browse pgsql-general by date

  From Date Subject
Next Message nkunkov 2006-07-14 19:34:47 Re: Dynamic table with variable number of columns
Previous Message Bruno Wolff III 2006-07-14 18:50:28 Re: Dynamic table with variable number of columns