Re: [BUGS] BUG #3362: xlog corruption just after initdb on irix

2007-06-06 Thread Herve Boulouis
Le 05/06/2007 17:33, Simon Riggs a ?crit: > On Tue, 2007-06-05 at 14:42 +, 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, yet its flaky when it comes back up t

Re: [BUGS] BUG #3362: xlog corruption just after initdb on irix

2007-06-06 Thread Herve Boulouis
Le 05/06/2007 12:06, Tom Lane a ?crit: > > > I had already noticed that problem on this platform with 8.0 or 8.1, but > > didn't report it at the time. > > You should have mentioned it earlier :-( ... whatever the problem is > is surely now long-forgotten. Although I see we have a report of 8.

Re: [BUGS] BUG #3362: xlog corruption just after initdb on irix

2007-06-06 Thread Heikki Linnakangas
Herve Boulouis wrote: Le 05/06/2007 17:33, Simon Riggs a écrit: On Tue, 2007-06-05 at 14:42 +, 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, yet its flaky when it co

[BUGS] BUG #3368: plperl error handling fails

2007-06-06 Thread Bart Degryse
The following bug has been logged online: Bug reference: 3368 Logged by: Bart Degryse Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.4 Operating system: Windows XP Professional Description:plperl error handling fails Details: I'm writing a function that fe

Re: [BUGS] BUG #3362: xlog corruption just after initdb on irix

2007-06-06 Thread Herve Boulouis
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 +, Herve Boulouis wrote: > >> > >>Well, I'd question what's going on with the hardware/filesystem or the > >>settings you've chosen for fsync a

Re: [BUGS] BUG #3362: xlog corruption just after initdb on irix

2007-06-06 Thread Herve Boulouis
Le 05/06/2007 12:06, Tom Lane a ?crit: > > I'm willing to take a look, but first please see if you can eliminate > the compiler-bug theory. Check to see if there's a newer compiler > version available; check whether building with CFLAGS=-O0 makes the > problem go away. quick question : do you t

Re: [BUGS] BUG #3362: xlog corruption just after initdb on irix

2007-06-06 Thread Tom Lane
Herve Boulouis <[EMAIL PROTECTED]> writes: > quick question : do you think that the --enable-integer-datetimes configure > flag could have an impact on this problem ? I doubt it. regards, tom lane ---(end of broadcast)--- T

Re: [BUGS] BUG #3362: xlog corruption just after initdb on irix

2007-06-06 Thread Tom Lane
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 note in the pg irix faq to use the 7.4.4m version > of mipspro when building the sour

Re: [BUGS] BUG #3362: xlog corruption just after initdb on irix

2007-06-06 Thread Herve Boulouis
Le 05/06/2007 12:06, Tom Lane a ?crit: > > I'm willing to take a look, but first please see if you can eliminate > the compiler-bug theory. Check to see if there's a newer compiler > version available; check whether building with CFLAGS=-O0 makes the > problem go away. I tried -O0 with same res

Re: [BUGS] BUG #3326: Invalid lower bound of autovacuum_cost_limit

2007-06-06 Thread Alvaro Herrera
Galy Lee wrote: Hi Galy, > The following bug has been logged online: > > Bug reference: 3326 > Logged by: Galy Lee > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.3 > Operating system: Red Hat 4. > Description:Invalid lower bound of autovacuum_cost_limit >