The following bug has been logged online:
Bug reference: 3362
Logged by: Herve Boulouis
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: IRIX 6.5.26
Description:xlog corruption just after initdb on irix
Details:
what I did:
- compile
Le 05/06/2007 17:33, Simon Riggs a ?crit:
> On Tue, 2007-06-05 at 14:42 +0000, Herve Boulouis wrote:
>
> Well, I'd question what's going on with the hardware/filesystem or the
> settings you've chosen for fsync and wal_fsync.
>
> If you shut it down cleanly, ye
akes the
> problem go away.
I'll try without optimizations.
Regards,
--
Herve Boulouis
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Le 06/06/2007 08:24, Heikki Linnakangas a ?crit:
> Herve Boulouis wrote:
> >Le 05/06/2007 17:33, Simon Riggs a ?crit:
> >>On Tue, 2007-06-05 at 14:42 +0000, Herve Boulouis wrote:
> >>
> >>Well, I'd question what's going on with the hardware/filesyst
quick question : do you think that the --enable-integer-datetimes configure
flag could have an impact on this problem ?
--
Herve Boulouis
---(end of broadcast)---
TIP 6: explain analyze is your friend
o verify this theory. Anyway,
maybe you should a add a note in the pg irix faq to use the 7.4.4m version
of mipspro when building the sources ?
--
Herve Boulouis
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Le 06/06/2007 18:04, Tom Lane a ?crit:
Hi,
> Herve Boulouis <[EMAIL PROTECTED]> writes:
> > The mipspro compiler is a proprietary product and I cannot get the
> > necessary updates so for now I am unable to verify this theory. Anyway,
> > maybe you should a add a not