Closed Bug 314490 (meta-pg) Opened 19 years ago Closed 18 years ago

[PostgreSQL] meta-bug tracking issues specific to Pg

Categories

(Bugzilla :: Database, defect)

Product:
Bugzilla
Component:
Database
Version:
2.21
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
Bugzilla 2.22

People

(Reporter: LpSolit, Unassigned)

References

(Depends on 4 open bugs,
URL
)

Details

(Keywords: meta)

Bug 98304 is fixed, but there are still many issues when using PostgreSQL, both version 7 and 8. This meta-bug will also help the QA team to track these PostgreSQL-specific bugs. mkanat, justdave: what is the status of the Bugzilla support for PostgreSQL in 2.22? For 2.20, we said it was still experimental. Is that still the case for 2.22 or do we want a real support? If we want a real support for Pg in 2.22, we have a lot of work to do before the next release.
Depends on: 314547
Depends on: 314919
Depends on: 315129
Alias: meta-pg
Depends on: 315535
Depends on: 316971
Depends on: 320289
Depends on: 320291
Depends on: 323575
All (known) crashers should be fixed for 2.22. As far as I can see, that's actually the case. Selenium will probably tell us if there is something wrong on qa222pg.
Target Milestone: --- → Bugzilla 2.22
Depends on: 323721
Depends on: 325048
Depends on: 327289
Depends on: 330365
PostgreSQL is now fully supported, and there is no known major problems running Bugzilla 2.22+ on it. Marking this bug as fixed.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Depends on: 257351
Depends on: 410115
You need to log in before you can comment on or make changes to this bug.