Opened 11 years ago
Closed 11 years ago
#2512 closed defect (fixed)
[raster]: raster_columns should support foreign tables and materialized views
| Reported by: | robe | Owned by: | Bborie Park |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 2.1.1 |
| Component: | raster | Version: | 2.1.x |
| Keywords: | history | Cc: |
Description
I haven't tested this, but looking at the raster_columns view it looks like it's missing relkind for materialized views and foreign tables similar to issue in #2511
should be changed to
c.relkind = 'r'::"char" OR c.relkind = 'v'::"char" OR c.relkind = 'm'::"char" OR c.relkind = 'f'::"char"
unfortunately foreign tables and materialized views never have constraints so the ability to get the other relevant info will be limited non-existent.
I wouldn't bother pushing to 2.0 since I think the user base of people that would try to use a PostgreSQL FDW in 9.2 and using raster and caring about raster_columns is really small if existent at all.
Change History (2)
comment:1 by , 11 years ago
| Status: | new → assigned |
|---|
comment:2 by , 11 years ago
| Keywords: | history added |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Fixed in trunk as of r12051. Fixed for 2.1 as of r12052