[BUGS] 7.3.5 initdb failure on Irix 6.5.18

2004-01-15 Thread Craig Ruff
same system works fine. Has anyone fixed this yet? If not, does anyone have hints that I can pursue since I have the source compiled up with debugging enabled? -- Craig Ruff NCAR[EMAIL PROTECTED] (303) 497-1211 P.O. Box 3000

Re: [BUGS] 7.3.5 initdb failure on Irix 6.5.18

2004-01-15 Thread Craig Ruff
On Thu, Jan 15, 2004 at 04:42:50PM -0500, Tom Lane wrote: > It would seem that the culprit must be somewhere in the 7.3.2-to-7.3.4 > changes in xlog.c: > ... > but I sure don't see anything there that looks like a potential > portability issue. I have some further info. 7.3.5 compiled with MIPSpr

Re: [BUGS] 7.3.5 initdb failure on Irix 6.5.18

2004-01-16 Thread Craig Ruff
Ok, I have further information on this problem. I believe it is a compiler problem. PostgreSQL version 7.3.3 is also affected when compiled with the MIPSpro 7.4.1 compiler, but when compiled with MIPSpro 7.4 it is ok. Using the gcc compiled version of backend/access/transam/xlog.c, I have gotten

Re: [BUGS] 7.3.5 initdb failure on Irix 6.5.18

2004-01-21 Thread Craig Ruff
Here is what I discovered about this problem. The MIPSpro 7.4.1 C compiler apparently has a structure assignment code generation bug that is triggered at backend/access/transam/xlog.c:2683 LogwrtResult.Write = LogwrtResult.Flush = EndOfLog; EndOfLog and LogwrtResult.Write are correct, bu

[BUGS] Irix initdb failure problem now fixed

2004-04-22 Thread Craig Ruff
now report that postgresql 7.4.2 now works under Irix 6.5.22 when compiled with the MIPSpro 7.4.2m C compiler. -- Craig Ruff NCAR[EMAIL PROTECTED] (303) 497-1211 P.O. Box 3000 Boulder, CO 80307 ---(e

[BUGS] Deadlock or other hang while vacuuming?

2004-11-08 Thread Craig Ruff
e serverlog output, other than the normal connection and transaction log messages. At this point, I'm ready to exclude the enumeration sessions from starting when the vacuum is active, but I thought I'd try and gather information just in case it is a problem in PostgreSQL. Does anyone h

Re: [BUGS] Deadlock or other hang while vacuuming?

2004-11-09 Thread Craig Ruff
On Mon, Nov 08, 2004 at 08:06:02PM -0500, Tom Lane wrote: > I believe that if VACUUM wants to delete a tuple that is on the same > physical page that a cursor is currently stopped on, the vacuum has to > wait until the cursor moves off that page. So the vacuum could > definitely be blocked by the

[BUGS] BUG #1418: RFC: Challenge/response authentication support

2005-01-19 Thread Craig Ruff
The following bug has been logged online: Bug reference: 1418 Logged by: Craig Ruff Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0 Operating system: Any Description:RFC: Challenge/response authentication support Details: PAM supports challenge response