On Tue, Mar 19, 2019 at 01:59:34PM -0300, Alvaro Herrera wrote: > On 2019-Mar-19, Andres Freund wrote: > > > Hi, > > > > On 2019-03-19 12:51:39 -0400, Tom Lane wrote: > > > David Fetter <da...@fetter.org> writes: > > > > I think the answer is "no," and we should deprecate this misfeature. > > > > It's bad enough that we'll be supporting it for five years after > > > > deprecating it, but it's worse to leave it hanging around our necks > > > > forever. https://en.wikipedia.org/wiki/Albatross_(metaphor) > > > > > > The problem with that approach is that not everybody agrees that > > > it's a misfeature. > > > > Yea, it's extremely useful to just be able to send a whole script to the > > server. Otherwise every application wanting to do so needs to be able to > > split SQL statements, not exactly a trivial task. And the result will be > > slower, due to increased rountrips. > > I suppose it can be argued that for the cases where they want that, it > is not entirely ridiculous to have it be done with a different API call, > say PQexecMultiple.
Renaming it to emphasize that it's a non-default choice seems like a large step in the right direction. Best, David. -- David Fetter <david(at)fetter(dot)org> http://fetter.org/ Phone: +1 415 235 3778 Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
