Re: rw_redis_fdw: SQL Errors when statement is within a function

From: GPT <gptmailinglists(at)gmail(dot)com>
To: Christoph Moench-Tegeder <cmt(at)burggraben(dot)net>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: rw_redis_fdw: SQL Errors when statement is within a function
Date: 2018-10-26 07:31:18
Message-ID: CADep2PNC2f57EL8ZtKb999oXvYWNBok74m033xMRG4AFw03fMQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I have searched in
https://github.com/nahanni/rw_redis_fdw/blob/master/redis_fdw.c for
PREPARE and EXECUTE keywords. There are not any of them, except in
comments.

So, the developer doesn´t use any PREPARE, EXECUTE statements.

So, this change occurs internally. If I am correct then the PG fails
to respond properly.

Tia

On 10/25/18, Christoph Moench-Tegeder <cmt(at)burggraben(dot)net> wrote:
> ## GPT (gptmailinglists(at)gmail(dot)com):
>
>> So, this kind of switch after a few goes is a normal behavior or
>> something unexpected which will change in future?
>
> It's expected, and even documented (when you look at the user-level
> interface):
> https://www.postgresql.org/docs/current/static/sql-prepare.html
> Prepared statements can use generic plans rather than re-planning
> with each set of supplied EXECUTE values. This occurs immediately
> for prepared statements with no parameters; otherwise it occurs
> only after five or more executions produce plans whose estimated
> cost average (including planning overhead) is more expensive than
> the generic plan cost estimate.
>
> Regards,
> Christoph
>
> --
> Spare Space.
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alexandre Assouad 2018-10-26 08:17:12 Re: Postgresql issue: FATAL: dsa_allocate could not find 7 free pages
Previous Message Thomas Munro 2018-10-25 22:58:40 Re: Postgresql issue: FATAL: dsa_allocate could not find 7 free pages