Steven Erickson wrote
> My problem now is that SELECTs scan all child tables
And what do these SELECTs look like - specifically the WHERE clauses?
David J.
--
View this message in context:
http://postgresql.nabble.com/Constraints-and-inheritance-tp5840715p5840716.html
Sent from the PostgreS
I have a table that has over 100K rows of GIS data, including a raster and an
insertdatetime timestamp columns. This table is continually loaded with data
with processes on the back side querying the data and populating other tables
depending on characteristics of the data. Today a row is rea
