Is that the direction we want to go, or would it be better to factor
the information out into a separate page about compatibility gotchas?
It would probably be better to explain globally applicable issues in a
separate section.
I agree that a general caveat is better, together with a one line
reference in the documentation of each table with an issue.
--
Fabien.
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
