12-21-2011 10:41 AM
12-21-2011 10:45 AM
PostgreSQL 8.3 is not supported anymore for two reasons:
unnest
) that was
added in PostgreSQL 8.4.foo*
) works thanks to new features of the GIN index type that were
introduced in PostgreSQL 8.4.Although the first point could be worked around, the second cannot if you want to keep fulltext prefix search.
(Note also that PostgreSQL 8.3 is getting old and we can't see any compelling reason that would justify avoiding an upgrade to a more recent version of PostgreSQL — PostgreSQL 9.1 is worth it if only for performance reasons.)
12-21-2011 10:45 AM
PostgreSQL 8.3 is not supported anymore for two reasons:
unnest
) that was
added in PostgreSQL 8.4.foo*
) works thanks to new features of the GIN index type that were
introduced in PostgreSQL 8.4.Although the first point could be worked around, the second cannot if you want to keep fulltext prefix search.
(Note also that PostgreSQL 8.3 is getting old and we can't see any compelling reason that would justify avoiding an upgrade to a more recent version of PostgreSQL — PostgreSQL 9.1 is worth it if only for performance reasons.)
12-16-2013 10:52 AM
You must have gotten this question a lot to post and answer your own question in 4 minutes
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.