Re: Optimise default partition scanning while adding new partition

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Amit Langote <amitlangote09(at)gmail(dot)com>, Jeevan Ladhe <jeevan(dot)ladhe(at)enterprisedb(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Optimise default partition scanning while adding new partition
Date: 2017-10-12 19:18:37
Message-ID: CA+TgmoarvRknFtUm46f25=vD4M5H7LN=cxEQRnufNSAHyngd6A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 5, 2017 at 9:29 PM, Amit Langote
<Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> Attached a patch to modify the INFO messages in check_default_allows_bound.

Committed. However, I didn't see a reason to adopt the comment change
you proposed, so I left that part out.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-10-12 19:22:16 Re: How does postgres store the join predicate for a relation in a given query
Previous Message Robert Haas 2017-10-12 19:08:10 Re: postgres_fdw super user checks