Hi,
On Thu, Sep 08, 2022 at 11:06:51AM +0200, Drouvot, Bertrand wrote:
> Hi,
>
> On 9/8/22 8:50 AM, Julien Rouhaud wrote:
>
> Thanks for looking at it!
>
> > On Thu, Sep 08, 2022 at 02:23:19PM +0900, Michael Paquier wrote:
> > > On Wed, Sep 07, 2022 at 06:19:42PM -0700, Jeremy Schneider wrote:
On Thu, Sep 08, 2022 at 02:23:19PM +0900, Michael Paquier wrote:
> On Wed, Sep 07, 2022 at 06:19:42PM -0700, Jeremy Schneider wrote:
> > I didn't fully debug yet, but here's the backtrace on my 14.4 build with
> > the patch
>
> What happens on HEAD? That would be the target branch for a new
> fea
On Wed, Sep 07, 2022 at 06:19:42PM -0700, Jeremy Schneider wrote:
> I didn't fully debug yet, but here's the backtrace on my 14.4 build with
> the patch
What happens on HEAD? That would be the target branch for a new
feature.
--
Michael
signature.asc
Description: PGP signature
Hi,
On 2022-08-31 11:00:05 -0700, Jeremy Schneider wrote:
> On 8/31/22 9:08 AM, Andres Freund wrote:
> >
> > I suspect we should carve out things like CALL, PREPARE, EXECUTE from
> > track_utility - it's more or less an architectural accident that they're
> > utility statements. It's a bit less
st 31. 8. 2022 v 17:50 odesílatel Pavel Stehule
napsal:
> Hi
>
>
> st 31. 8. 2022 v 17:34 odesílatel Drouvot, Bertrand
> napsal:
>
>> Hi hackers,
>>
>> While query jumbling is provided for function calls that’s currently not
>> the case for procedures calls.
>> The reason behind this is that all
Hi,
On 2022-08-31 17:33:44 +0200, Drouvot, Bertrand wrote:
> While query jumbling is provided for function calls that’s currently not the
> case for procedures calls.
> The reason behind this is that all utility statements are currently
> discarded for jumbling.
> [...]
> That’s why we think it wo
Hi
st 31. 8. 2022 v 17:34 odesílatel Drouvot, Bertrand
napsal:
> Hi hackers,
>
> While query jumbling is provided for function calls that’s currently not
> the case for procedures calls.
> The reason behind this is that all utility statements are currently
> discarded for jumbling.
>
> We’ve re