|
|
Matt Bertrand created an issue |
|
Problem importing a data catalog with long abstracts in PostgreSQL |
|
Issue Type: |
|
|---|---|
|
Affects Versions: |
2.4.5, Community |
|
Assignee: |
|
|
Components: |
JDBCConfig |
|
Created: |
07/Mar/14 1:31 PM |
|
Environment: |
Ubuntu 12.04, PostgreSQL 9.1, Tomcat 6 |
|
Priority: |
|
|
Reporter: |
Minor|
Current database schema won’t allow for object_property.value longer than 255 characters, and for our geoserver instance, layer abstracts often exceed that length. I tried changing the type of object_property.value from varchar(255) to text, but ran into another problem with indexes on this field: some abstracts are over 2712 characters, which is the maximum size of an index in Postgres (“ERROR: index row size exceeds maximum 2712 for index”) Would removing these indices cause a significant performance hit? Better to limit the abstract size? > 255 but < 2712? |
|
|
|
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) |
|
|
