pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

transaction ID wrap limit
2+ messages / 2 participants
[nested] [flat]

* transaction ID wrap limit
@ 2006-12-18 09:26  Sabin Coanda <sabin.coanda@deuromedia.ro>
  0 siblings, 1 reply; 2+ messages in thread

From: Sabin Coanda @ 2006-12-18 09:26 UTC (permalink / raw)
  To: pgsql-performance

Hi all,

A vacuum full command logs the message:
... LOG:  transaction ID wrap limit is 1073822617, limited by database "A"

Sometimes ago, the vacuum full logged:
... LOG:  transaction ID wrap limit is 2147484148, limited by database "A"

What causes that difference of the limit ? Should I set or optimize 
something on my Postgresql server ?

TIA,
Sabin 





^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: transaction ID wrap limit
@ 2006-12-18 15:51  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Sabin Coanda <sabin.coanda@deuromedia.ro>
  0 siblings, 0 replies; 2+ messages in thread

From: Tom Lane @ 2006-12-18 15:51 UTC (permalink / raw)
  To: Sabin Coanda <sabin.coanda@deuromedia.ro>; +Cc: pgsql-performance

"Sabin Coanda" <sabin.coanda@deuromedia.ro> writes:
> A vacuum full command logs the message:
> ... LOG:  transaction ID wrap limit is 1073822617, limited by database "A"

> Sometimes ago, the vacuum full logged:
> ... LOG:  transaction ID wrap limit is 2147484148, limited by database "A"

> What causes that difference of the limit ?

The limit is *supposed* to advance.  The fact that it jumped this much
in one step suggests you're not vacuuming often enough :-(

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 2+ messages in thread

end of thread, other threads:[~2006-12-18 15:51 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-12-18 09:26 transaction ID wrap limit Sabin Coanda <sabin.coanda@deuromedia.ro>
2006-12-18 15:51 ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox