Require PostgreSQL 8

catch - April 18, 2008 - 09:25
Project:Drupal
Version:7.x-dev
Component:database system
Category:task
Priority:normal
Assigned:Unassigned
Status:closed
Description

We've upped MySQL requirements to 5.0, how about postgres?

AttachmentSize
postgres-8.patch1.06 KB

#1

sammys - July 10, 2008 - 07:58
Status:patch (code needs review)» patch (reviewed & tested by the community)

Since we're moving MySQL up to 5.0 there's no reason for us to support 7.4 PostgreSQL anymore especially because transaction support will be much nicer in PostgreSQL 8.x and beyond.

Any complaints? Voice them now!

#2

Damien Tournoud - July 10, 2008 - 08:35

Ok for the principle. I even suggest we recommend the latest stable version (ie PostgreSQL 8.3, as of today).

We should also add that requirement to the INSTALL.TXT file.

#3

catch - July 10, 2008 - 08:58
Status:patch (reviewed & tested by the community)» patch (code needs review)

Re-rolled for 8.4.

AttachmentSize
postgres.patch629 bytes

#4

catch - July 10, 2008 - 09:14

Umm. 8.3

AttachmentSize
postgres_4.patch629 bytes

#5

Crell - July 11, 2008 - 15:01

I have no idea what the distribution of Postgres installations is or what the support cycle is for older versions of Postgres. However, I am all in favor of supporting fewer versions of a database so that we have fewer bugs to work around. :-) D7 does sound like the time to do it, too. The only copy of Postgres I have available to me is 8.3. So I'm +1 on upping the requirement to, um, whatever. :-)

#6

bjaspan - July 11, 2008 - 22:07

I developed and tested Schema API for pgsql 8. It's possible we already don't support 7.x.

#7

linuxpoet - July 11, 2008 - 22:08

7.4 is likely to be EOL by the end of the year. I would actually suggest having a requirement of 8.1 as 8.1 is the first release that has two very important technologies:

PITR
Partitioning/constraint_exclusion

As well as several specific performance enhancements.

#8

catch - July 11, 2008 - 22:18

Here's the patches. One of them has to be RTBC ;)

AttachmentSize
postgres-8-3.patch629 bytes
postgres-8-2.patch629 bytes
postgres-8-1.patch629 bytes
postgres-8-0.patch629 bytes

#9

David Strauss - July 11, 2008 - 23:16

+1 on dropping support for PgSQL 7. We already have enough trouble finding testers for any version of Postgres. Plus, Postgres users are unlikely to be on cheap shared hosting where they're locked into an old version.

#10

nbz - July 12, 2008 - 15:58

From what I can see, RHEL/Centos 5 comes with version 8.1, so that may be a good minimum target. (but then again, it has php version 5.1.6+patches too... potentially not meeting the php requirements.)

#11

Crell - July 13, 2008 - 19:05
Status:patch (code needs review)» patch (reviewed & tested by the community)

Debian Stable (Etch) currently ships with both 7.4 and 8.1.

The now-retired Ubuntu Edgy also offers both 7.4 and 8.1, so I think it's a safe bet that Hardy (the current stable LTS release) offers at least 8.1.

It sounds to me like 8.1 is a safe version to target, as all of the majors support it already. I am marking this RTBC for the 8.1 patch in #8.

#12

chx - July 13, 2008 - 21:30

Another vote for 8.1 -- if we are bent on supporting pgsql then be it 8.1.

#13

Dries - July 14, 2008 - 17:26
Status:patch (reviewed & tested by the community)» fixed

Committed the 8.1 patch to CVS HEAD. Thanks.

#14

Anonymous (not verified) - July 31, 2008 - 04:46
Status:fixed» closed

Automatically closed -- issue fixed for two weeks with no activity.

 
 

Drupal is a registered trademark of Dries Buytaert.