| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Markus Wollny" <Markus(dot)Wollny(at)computec(dot)de> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Transaction wraparound problem with database postgres |
| Date: | 2008-03-21 21:44:47 |
| Message-ID: | 5262.1206135887@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Markus Wollny" <Markus(dot)Wollny(at)computec(dot)de> writes:
> Just some more info, hoping that it helps with a diagnosis:
> 1: datname (typeid = 19, len = 64, typmod = -1, byval = f)
> 2: age (typeid = 23, len = 4, typmod = -1, byval = t)
> 3: datfrozenxid (typeid = 28, len = 4, typmod = -1, byval = t)
> ----
> 1: datname = "postgres" (typeid = 19, len = 64, typmod = -1, byval = f)
> 2: age = "-2147321465" (typeid = 23, len = 4, typmod = -1, byval = t)
> 3: datfrozenxid = "1835116837" (typeid = 28, len = 4, typmod = -1, byval = t)
What are the datfrozenxid's of the other rows in pg_database?
Do the other fields of postgres' row look sane?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Wollny | 2008-03-21 21:46:50 | Re: Transaction wraparound problem with database postgres |
| Previous Message | Edoardo Panfili | 2008-03-21 21:42:25 | C function and enum types parameters |