On Fri, Jan 11, 2019 at 8:01 PM Tom Lane wrote:
>
> Amit Kapila writes:
> > On Fri, Jan 11, 2019 at 5:00 AM Tom Lane wrote:
> >> It's also possible that you just aren't exercising the cases where
> >> trouble occurs. In particular, noting this bit in InsertOneValue():
> >> OidOutputFunctionCall
Amit Kapila writes:
> On Fri, Jan 11, 2019 at 5:00 AM Tom Lane wrote:
>> It's also possible that you just aren't exercising the cases where
>> trouble occurs. In particular, noting this bit in InsertOneValue():
>> OidOutputFunctionCall(typoutput, values[i];
> I have tried initdb with --debu
On Fri, Jan 11, 2019 at 5:00 AM Tom Lane wrote:
> It's also possible that you just aren't exercising the cases where
> trouble occurs. In particular, noting this bit in InsertOneValue():
>
> /*
> * We use ereport not elog here so that parameters aren't evaluated unless
> * the messa
John Naylor writes:
> Thought I'd ping...
Sorry, I'd not been paying attention to this thread.
> On Sat, Dec 15, 2018 at 12:02 AM Amit Kapila wrote:
>> As pointed out by John Naylor [1], it seems during bootstrap mode, we
>> are always creating FSM files which are not required. In commit's
>>
Thought I'd ping...
(sorry for the top post)
On Sat, Dec 15, 2018 at 12:02 AM Amit Kapila wrote:
>
> As pointed out by John Naylor [1], it seems during bootstrap mode, we
> are always creating FSM files which are not required. In commit's
> b9d01fe288 and 3908473c80, we have added some code wher
