Closed Bug 385366 Opened 19 years ago Closed 19 years ago

Perl crash when using PostgreSQL

Categories

(Bugzilla :: Database, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

VERIFIED INVALID

People

(Reporter: bruce.rindahl, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a6pre) Gecko/20070620 Minefield/3.0a6pre Build Identifier: Bugzilla 3.0 Using ActiveState perl v5.8.8 for MSWin32-x-multi-thread. Bugzilla 3.0. PostgreSQL 8.2.0 After installing all the perl modules including DBD-Pg I edited localconfig to: $db_driver = 'pg'; When running checksetup.pl again it checks for perl modules, then Reading ./localconfig... Checking for DBD-Pg (v1.45) ok: found v1.45 At this point I get the Microsoft Error Box. The title is "Perl Command Line Interperter". The message is "Perl Command Line Interperter has encountered a problem and needs to close." The details window says: "An unhandled win32 exception occured in perl.exe [3892]" There are additional comments about Just-In-Time debugging. Reproducible: Always Steps to Reproduce: 1. 2. 3. Note when I change localconfig to: $db_driver = 'mysql'; I get a clean and fully functional bugzilla after it configures mySQL. We use PostgreSQL for our server and I would like to use it for Bugzilla.
The identical behavior occurs on WindowsXP (SP2) and Windows Server 2003
That sounds like a bug in DBD::Pg, to me. You might want to check this list of DBD::Pg bugs here: http://rt.cpan.org/Public/Dist/Display.html?Name=DBD-Pg Also, try upgrading to a newer version of DBD-Pg.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
I upgraded DBD-Pg to version 1.49 and it worked fine. Thanks for the tip. Sorry I didn't look around a bit harder. Might want to consider requiring the 1.49 version in the install. Thanks!
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.