| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | enable_constraint_exclusion GUC name |
| Date: | 2005-08-19 20:56:18 |
| Message-ID: | 200508192056.j7JKuIu04788@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Is enable_constraint_exclusion the proper name for this feature? I know
we have enable* in the optimizer settings, but that naming seems
unfortunate in that we should have just called it hash_join and it could
be enabled/disabled.
I am thinking we should just call it constraint_exclusion.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-08-19 21:47:11 | Re: Why is lock not released? |
| Previous Message | Alvaro Herrera | 2005-08-19 18:35:38 | Re: Why is lock not released? |