In a PostgreSQL 8.0.4 environment, does dropping the database and reloading it
completely reset the XID information that causes transaction ID wraparound? (I
am assuming that it does, but wanted to double-check before doing this.)
>From what I can tell, I am just about to hit the XID wraparound p
Hi,
i use postgresql version7.4.7 on i386-pc-linux-gnu, autovacuum is
configured to run on this database.
But recently, we lost data for a database, we were able to connect the
database but we couldn't see any table anymore.
I suspected a transaction ID wraparound, and to fix it, i just
imp
"Bill Bartlett" <[EMAIL PROTECTED]> writes:
> In a PostgreSQL 8.0.4 environment, does dropping the database and
> reloading it completely reset the XID information that causes
> transaction ID wraparound?
I gather from the reference to "d:" that you're running on Windows.
You really, really, reall
[EMAIL PROTECTED] writes:
> i use postgresql version7.4.7 on i386-pc-linux-gnu, autovacuum is
> configured to run on this database.
Hmm ... in theory autovacuum should have kept you out of trouble,
if it was working properly. Were you keeping an eye on its log
output?
> Doing a manual vacuumdb
On Jun 21, 2008, at 8:47 AM, [EMAIL PROTECTED] wrote:
i use postgresql version7.4.7 on i386-pc-linux-gnu, autovacuum is
configured to run on this database.
But recently, we lost data for a database, we were able to connect
the database but we couldn't see any table anymore.
I suspected a trans
