>
>Thanks Shaun!
>
>Yes, we're getting synchronous_commit on right now.
>
>The log_min_duration was briefly set to 0 at the time I sent out the post,
>just to see what statements were logged right before everything went to
>hell. Didn't yield much since we very quickly realized we couldn't cope
>wi
Hi Jerry,
Thanks for the suggestion
Yes, until about a month ago, we weren't wrapping our snapshots with
pg_start_backup and pg_stop_backup. Same reason as you mentioned, the
database would start up and "trivial checks" would be okay, and so we
figured "why write a script?".
However we did chang
"Anand Kumar, Karthik" writes:
> Thanks Shaun!
>
> Yes, we're getting synchronous_commit on right now.
>
> The log_min_duration was briefly set to 0 at the time I sent out the post,
> just to see what statements were logged right before everything went to
> hell. Didn't yield much since we very q
Thanks Shaun!
Yes, we're getting synchronous_commit on right now.
The log_min_duration was briefly set to 0 at the time I sent out the post,
just to see what statements were logged right before everything went to
hell. Didn't yield much since we very quickly realized we couldn't cope
with the vol
On 12/19/2013 12:42 PM, Anand Kumar, Karthik wrote:
> ERROR: index "mv_visits_p03_n2" contains unexpected zero page at block
> 15939
> ERROR: invalid page header in block 344713 of relation
> pg_tblspc/4376157/PG_9.1_201105231/16393/8367465
I don't care what kind of checks your admins have perf
Hi,
We're looking for help with possible corruption of our indexes and tables.
Seemingly in the middle of normal operations, we will run into errors like
the below:
ERROR: index "mv_visits_p03_n2" contains unexpected zero page at block
15939
ERROR: invalid page header in block 344713 of relati
