I am thinking we should just call it constraint_exclusion.
So, given the silence on this, I assume people think we should rename
this before beta starts.
Well it depends either one seems correct per the postgresql.conf. For
example enable_seqscan, or "add"_missing_from_clause.
It seems that if the postgresql.conf parameter is actually causing a
different behavior we tend to note the behavior in the prefix (thus
enable/add) but that if it is more general we done (thus log_) .
I don't care either way but it seemed something to note before the
decision was made.
Sincerely,
Joshua D. Drake
--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
