On Wed, Feb 17, 2016 at 7:23 PM, Masahiko Sawada wrote:
> On Wed, Feb 17, 2016 at 7:14 PM, Robert Haas wrote:
>> On Wed, Feb 17, 2016 at 3:22 PM, Masahiko Sawada
>> wrote:
>>> On Sat, Feb 13, 2016 at 2:45 PM, Robert Haas wrote:
On Fri, Feb 12, 2016 at 1:35 PM, Payal Singh wrote:
> Th
On Wed, Feb 17, 2016 at 7:14 PM, Robert Haas wrote:
> On Wed, Feb 17, 2016 at 3:22 PM, Masahiko Sawada
> wrote:
>> On Sat, Feb 13, 2016 at 2:45 PM, Robert Haas wrote:
>>> On Fri, Feb 12, 2016 at 1:35 PM, Payal Singh wrote:
The feature seems to work as described, but is it necessary to enc
On Wed, Feb 17, 2016 at 3:22 PM, Masahiko Sawada wrote:
> On Sat, Feb 13, 2016 at 2:45 PM, Robert Haas wrote:
>> On Fri, Feb 12, 2016 at 1:35 PM, Payal Singh wrote:
>>> The feature seems to work as described, but is it necessary to enclose
>>> multiple GUC settings in a parenthesis? This seems
On Sat, Feb 13, 2016 at 2:45 PM, Robert Haas wrote:
> On Fri, Feb 12, 2016 at 1:35 PM, Payal Singh wrote:
>> The feature seems to work as described, but is it necessary to enclose
>> multiple GUC settings in a parenthesis? This seems a deviation from the
>> usual syntax of altering multiple set
On Fri, Feb 12, 2016 at 1:35 PM, Payal Singh wrote:
> The feature seems to work as described, but is it necessary to enclose
> multiple GUC settings in a parenthesis? This seems a deviation from the usual
> syntax of altering multiple settings separated with comma.
Well, note that you can say:
The following review has been posted through the commitfest application:
make installcheck-world: tested, failed
Implements feature: tested, passed
Spec compliant: tested, failed
Documentation:not tested
When running gmake installcheck for regression tests, 2 tests are
