Re: move PartitionBoundInfo creation code

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: move PartitionBoundInfo creation code
Date: 2018-11-13 13:35:11
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Tue, Nov 13, 2018 at 09:58:08AM -0300, Alvaro Herrera wrote:
> "the context that was active when the function was called" is typically
> expressed simply as "the current memory context". Perhaps the whole
> phrase can be reduced to "The object returned by this function is wholly
> allocated in the current memory context"?

Yes, that looks cleaner. I am planning to do a last lookup round on
tomorrow morning my time before committing, so I may still tweak a
couple of other words...

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2018-11-13 13:35:24 proposal - plpgsql unique statement id
Previous Message Amit Kapila 2018-11-13 13:26:09 Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query