Hi,
I know I'm 7 months late to this, but only just read the beta 4 release notes.
Is there anything people using float datetimes can do that isn't a
pg_dumpall | pg_restore to do a less painful update?
We have several TB of data still using float datetimes and I'm trying
to figure out how we
We had the same issues running 9.2.4:
[2013-10-15 00:23:01 GMT/0/15396] WARNING: page 8789807 of relation
base/16429/2349631976 is uninitialized
[2013-10-15 00:23:01 GMT/0/15396] CONTEXT: xlog redo vacuum: rel
1663/16429/2349631976; blk 8858544, lastBlockVacuumed 0
[2013-10-15 00:23:01
Hi,
How would one go about detecting whether they've lost rows due to the
relfrozenxid?
Unfortunately running 'SELECT txid_current() 2^31' on our DB returns
false, and I'm a little bit worried, since we've been seeing some
WeirdStuff(tm) lately.
We're only 200M txids or so past 2^31.
Thanks!
:
On Thu, Dec 5, 2013 at 4:14 PM, Omar Kilani omar.kil...@gmail.com wrote:
Hi,
How would one go about detecting whether they've lost rows due to the
relfrozenxid?
Unfortunately running 'SELECT txid_current() 2^31' on our DB returns
false, and I'm a little bit worried, since we've been seeing
