On Monday June 6 2005 11:15 pm, Tom Lane wrote:
> This doesn't really address the question of how the page
> header got clobbered in the first place, though. Did you by
> any chance make a dump to see what data was in there?
I couldn't start the postmaster at all with that data in the
cluster, s
On Monday June 6 2005 11:15 pm, Tom Lane wrote:
> It's possible that you are one minor release short of having
> dodged this problem, as I see in the 7.3.5 CVS log
>
> * src/backend/storage/buffer/bufmgr.c (REL7_3_STABLE): Force
> zero_damaged_pages to be effectively ON during recovery
"Ed L." <[EMAIL PROTECTED]> writes:
> Someone flipped a breaker switch, and evidently triggered
> corruption in one of our major clusters:
> 2005-06-06 14:31:11.984 [20124] PANIC: Invalid page header in block 22376
> of 79189398
It's possible that you are one minor release short of having dodg
On Mon, 2005-06-06 at 16:39, Ed L. wrote:
> On Monday June 6 2005 3:29 pm, Ed L. wrote:
> > On Monday June 6 2005 3:17 pm, Scott Marlowe wrote:
> > > On Mon, 2005-06-06 at 15:16, Ed L. wrote:
> > > > Someone flipped a breaker switch, and evidently triggered
> > > > corruption in one of our major cl
On Monday June 6 2005 3:29 pm, Ed L. wrote:
> On Monday June 6 2005 3:17 pm, Scott Marlowe wrote:
> > On Mon, 2005-06-06 at 15:16, Ed L. wrote:
> > > Someone flipped a breaker switch, and evidently triggered
> > > corruption in one of our major clusters:
> >
> > OK, if postgresql is running on hard
On Monday June 6 2005 3:17 pm, Scott Marlowe wrote:
> On Mon, 2005-06-06 at 15:16, Ed L. wrote:
> > Someone flipped a breaker switch, and evidently triggered
> > corruption in one of our major clusters:
>
> OK, if postgresql is running on hardware that doe NOT lie
> about fsyncing, and it is set to
On Mon, 2005-06-06 at 15:16, Ed L. wrote:
> Someone flipped a breaker switch, and evidently triggered
> corruption in one of our major clusters:
>
> $ cat server_log.Mon
> postmaster successfully started
> 2005-06-06 14:31:11.950 [20124] LOG: database system was interrupted being
> in recover
On Monday June 6 2005 2:16 pm, Ed L. wrote:
> Someone flipped a breaker switch, and evidently triggered
> corruption in one of our major clusters:
BTW, this is a 7.3.4 cluster ...
Ed
---(end of broadcast)---
TIP 9: the planner will ignore your desi
Someone flipped a breaker switch, and evidently triggered
corruption in one of our major clusters:
$ cat server_log.Mon
postmaster successfully started
2005-06-06 14:31:11.950 [20124] LOG: database system was interrupted being in
recovery at 2005-06-06 14:29:01 EDT
This probably mean
