329538 - [PostgreSQL] Clean up Pg code now that we require Pg 8.3

Status: RESOLVED WORKSFORME

(Bugzilla :: Database, enhancement)

Description

[Max Kanat-Alexander]

There's a lot of code that can be a lot cleaner now that we require PostgreSQL 8.0.

Comment 1

[Frédéric Buclin]

This bug is retargetted to Bugzilla 3.2 for one of the following reasons:

- it has no assignee (except the default one)
- we don't expect someone to fix it in the next two weeks (i.e. before we freeze the trunk to prepare Bugzilla 3.0 RC1)
- it's not a blocker

If you are working on this bug and you think you will be able to submit a patch in the next two weeks, retarget this bug to 3.0.

If this bug is something you would like to see implemented in 3.0 but you are not a developer or you don't think you will be able to fix this bug yourself in the next two weeks, please *do not* retarget this bug.

If you think this bug should absolutely be fixed before we release 3.0, either ask on IRC or use the "blocking3.0 flag".

Comment 2

[Max Kanat-Alexander]

Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?". Then, either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.

This particular bug has not been touched in over eight months, and thus is being retargeted to "---" instead of "Bugzilla 4.0". If you believe this is a mistake, feel free to retarget it to Bugzilla 4.0.

Comment 3

[Frédéric Buclin]

(In reply to comment #0)
> There's a lot of code that can be a lot cleaner now that we require PostgreSQL
> 8.0.

For instance, besides bug 493027? :)

Comment 4

[Frédéric Buclin]

No reply to comment 3, so it's unclear what still needs to be done. Marking WFM.