[HACKERS] AllocFile debug code
http://archives.postgresql.org/pgsql-committers/2006-08/msg00410.php Should this be removed again now? The actual fix should be http://archives.postgresql.org/pgsql-committers/2006-08/msg00504.php, and per http://archives.postgresql.org/pgsql-hackers/2006-08/msg01920.php it seems to have solved the problem? (It does log the error for pgstat.stat on every single server startup, which is why I noticed it) //Magnus ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] AllocFile debug code
Magnus Hagander [EMAIL PROTECTED] writes: http://archives.postgresql.org/pgsql-committers/2006-08/msg00410.php Should this be removed again now? I was intending to remove it sometime before release, but seeing that a number of the Windows buildfarm members have been out of commission for the last several weeks, I'm unsure whether we have enough test runs yet to be sure the problem is fixed ... regards, tom lane ---(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
Re: [HACKERS] AllocFile debug code
http://archives.postgresql.org/pgsql-committers/2006-08/msg00410.php Should this be removed again now? I was intending to remove it sometime before release, but seeing that a number of the Windows buildfarm members have been out of commission for the last several weeks, I'm unsure whether we have enough test runs yet to be sure the problem is fixed ... Yeah, seems reasonable to keep around for a bit longer. It should probably be added to the release checklist so we remember to get it done before we roll RC at least? //Magnus ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] AllocFile debug code
Added to open items list. --- Tom Lane wrote: Magnus Hagander [EMAIL PROTECTED] writes: http://archives.postgresql.org/pgsql-committers/2006-08/msg00410.php Should this be removed again now? I was intending to remove it sometime before release, but seeing that a number of the Windows buildfarm members have been out of commission for the last several weeks, I'm unsure whether we have enough test runs yet to be sure the problem is fixed ... regards, tom lane ---(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 -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 6: explain analyze is your friend
