Magnus Hagander <[EMAIL PROTECTED]> writes:
> Could we dump it when it's non-default only? That way the people that
> *have* set a custom comment on it will still get it restored, just a
> failure in this case. The majority of people who *haven't* set a comment
> will not have the problem at all.
The patch seems ugly enough without wiring in knowledge of what the
standard comment is :-(
We don't dump non-default comments on other system objects either,
so I don't think it's out of line to suppress the one on schema public.
Perhaps at some point we should add something to pg_description to allow
distinguishing user-supplied comments from built-in ones, and then dump
any user-supplied comment on any system object. But not today ...
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
