Closed (fixed)
Project:
Views (for Drupal 7)
Version:
6.x-2.7
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Nov 2009 at 22:48 UTC
Updated:
24 Oct 2010 at 18:44 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedI saw the same thing exactly. The weird thing is, I can't see the new aggregate in the system, or I'm looking in the wrong place.. so although the CREATE AGGREGATE gave no errors, I can't find it.
Comment #2
Anonymous (not verified) commentedFYI, This error occurred on Postgres 8.1.17
It did not occur for a copy of the database/site running the same update on Postgres 8.3.7. Looks like IF EXISTS is handled ok in 8.3 .
Comment #3
andy_read commentedHaving looked through the Postgres docs, the "if exists" syntax has been introduced since 8.2, although it does describe this as a non-standard Postgres extension, even for things like "drop table if exists". But for that matter aggregates as a whole are not in the SQL standard.
I'm looking to upgrade my [conservative] Debian server to 8.2 or 8.3, which should improve Postgres compatibility with a number of modules, but can anyone tell me whether there is an agreed policy on which versions of Postgres should be supported? I recall reading somewhere that D7 would require at least 8.2 for some core functionality.
Comment #4
t-om commentedSeeing this too on an up-to-date CentOS 5.4 environment when trying to update the Views module from 6.x-2.6 to 6.x-2.8.
Drupal version 6.16.
Postgresql version 8.1.18.
In my case it was very serious, loosing sight of all the dynamic content of the site.
There seemed to be some Postgresql issues also on newer Views versions than 6.x-2.8.
Comment #5
merlinofchaos commentedD7 will only support Postgres 8.3 or better. According to the requirements page, Drupal core supports Postgress 7.4 or better. Views theoretically supports what core supports, but to be honest, almost no one has a version of postgres that old to test on. So issues like this are both 1) going to get through and 2) hard to fix.
Comment #6
Letharion commentedHello!
I'm cleaning up the Views issue queue, and thus trying to close open support requests that have had no activity in the past 6 months or more. If this is still a relevant please reset the status to active, and the new bug squad will make an attempt at the problem.