Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I understand that the function Populate_Geometry_Columns() inserts records in the geometry_columns table for geometry columns that are not yet listed there. However, an invocation of Probe_Geometry_Columns() reports:

select probe_geometry_columns();
 probed:1086 inserted:0 conflicts:1086 stale:53612
(1 row)

This is after a call to Populate_Geometry_Columns(). Is there an easy/documented way how to get rid of the conflicts and the stale entries?

EDIT: As per Darrell Fuhriman's answer on GIS.SX, there are three ways:

  • truncate the geometry_columns table and rerun SELECT probe_geometry_columns()
  • Run a custom script that operates on PostGis's internal tables
  • Upgrade to PostGis 2.0 or later
share|improve this question

closed as off-topic by Jack Douglas Aug 31 '13 at 13:55

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Too localized - this could be because your code has a typo, basic error, or is not relevant to most of our audience. Consider revising your question so that it appeals to a broader audience. As it stands, the question is unlikely to help other users (regarding typo questions, see this meta question for background)." – Jack Douglas
If this question can be reworded to fit the rules in the help center, please edit the question.

This isn't off-topic but it looks like you've already got your answer here. – Jack Douglas Aug 31 '13 at 13:54
@JackDouglas: Sorry, forgot about the double-post. Would add my edit as an answer but currently can't answer. – krlmlr Sep 1 '13 at 5:23