Re: Bulk persistence strategy

From: Riaan Stander <rstander(at)exa(dot)co(dot)za>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: "pgsql-performa(dot)" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Bulk persistence strategy
Date: 2017-05-22 09:36:01
Message-ID: 7258b091-8126-6c15-9b26-2f2938158514@exa.co.za
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


> On 22 May 2017 at 09:06, Riaan Stander <rstander(at)exa(dot)co(dot)za> wrote:
>
>>> It sounds like you don't know about anonymous code blocks with DO
>>> https://www.postgresql.org/docs/devel/static/sql-do.html
>>>
>> Yes I do know about that feature. My first implemented generated an
>> anonymous code block, but to my utter dismay once I tried actually doing
>> parameter binding from the application it did not work. This seems to be a
>> Postgres limitation actually stated in the documentation. The anonymous code
>> block is treated as a function body with no parameters.
>>
>> Thanks for the suggestion though.
> Perhaps we should look into parameterisable DO statements.
>
Now that I would second!!

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2017-05-22 11:50:15 Re: Bulk persistence strategy
Previous Message Simon Riggs 2017-05-22 08:27:25 Re: Bulk persistence strategy