| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Daniel Begin <jfd553(at)hotmail(dot)com> |
| Cc: | melvin6925 <melvin6925(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [NOVICE] Constraint exclusion in partitions |
| Date: | 2015-05-23 23:31:55 |
| Message-ID: | CAKFQuwZz2bC+DdXfgGOYcC+ZPg-AL2eqgfxr36t0xssQ5mSjgA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Saturday, May 23, 2015, Daniel Begin <jfd553(at)hotmail(dot)com> wrote:
> I am working with postgresql 9.3 and I understand from the documentation
> that constraint_exclusion is set to “partition” by default. Looking at my
> postgres.conf file, the concerned line is “#constraint_exclusion =
> partition”.
>
> Furthermore, the execution plan shows that constraint_exclusion was used
> at least for constant id and range of ids
>
> What is your question/concern?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2015-05-23 23:38:05 | Re: Trying to solve a SocketError [Errno 13] Permission with PL/Python in PostgreSQL 9.3 |
| Previous Message | Adrian Klaver | 2015-05-23 23:30:47 | Re: Trying to solve a SocketError [Errno 13] Permission with PL/Python in PostgreSQL 9.3 |