German Becker wrote:
I am testing version 9.1.9 before putting it in production. One of my tests
involved deleting a the
contents of a big table ( ~ 13 GB size) and then VACUUMing it. During VACUUM
PANICS. Here is the
message:
PANIC: corrupted item pointer: offset = 8128, size = 80
[please don't top-post]
German Becker german.bec...@gmail.com wrote:
Albe Laurenz laurenz.a...@wien.gv.at wrote:
German Becker wrote:
I am testing version 9.1.9 before putting it in production. One
of my tests involved deleting a the contents of a big table ( ~
13 GB size) and then
German Becker wrote:
Just in case there are some errors in my first email, where it says after
deleting the context of the
same big table It should say after deleting de contents of the same big
table I essence what i did
is
DELETE from table;
VACUUM table;
And I got the error
I am
OK I apologise for the lack of clarity of the first message. Let
me summarize the steps that lead me to the error.
I have 2 servers running Ubuntu 12.04 on which I am testing Postgres 9.1.9.
I set up streaming replication between them (no synchronous replication)
Both servers have 4 SATA hard
We recently moved to PG 9.2.4 (from 8.4.4) to take advantage of replication,
and I have to say it's pretty awesome.
I ran into some things that I was hoping someone could clarify.
a) There appears to be no way to tell how far behind my standby servers are.
That is, I can find a checkpoint
I can answer your first question. The way I check the replication delay is
by running this query on the replication server:
*SELECT now() - pg_last_xact_replay_timestamp();*
Of course you need to configure hot standby replication, which you should
if you are not.
Regards,
Strahinja
On Tue,
