Re: Bulk persistence strategy

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Riaan Stander <rstander(at)exa(dot)co(dot)za>, "pgsql-performa(dot)" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Bulk persistence strategy
Date: 2017-05-22 11:50:15
Message-ID: 64473.1495453815@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> It sounds like you don't know about anonymous code blocks with DO
> https://www.postgresql.org/docs/devel/static/sql-do.html

No, the problem was that there are also some parameters to be passed
in from the application, and DO doesn't take any parameters; so that
would require inserting them manually into the DO text, with all the
attendant hazards of getting-it-wrong.

We've speculated before about letting DO grow some parameter handling,
but it's not gotten to the top of anyone's to-do list.

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Ariel 2017-05-22 15:17:31 index of only not null, use function index?
Previous Message Riaan Stander 2017-05-22 09:36:01 Re: Bulk persistence strategy