Re: [HACKERS] Disallowing multiple queries per PQexec() - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: [HACKERS] Disallowing multiple queries per PQexec()
Date
Msg-id ade2f664-dbf9-546d-ece9-1816b5ecabaa@BlueTreble.com
Whole thread Raw
In response to Re: [HACKERS] Disallowing multiple queries per PQexec()  (Andres Freund <andres@anarazel.de>)
Responses Re: [HACKERS] Disallowing multiple queries per PQexec()  (Surafel Temesgen <surafel3000@gmail.com>)
List pgsql-hackers
On 2/28/17 2:45 PM, Andres Freund wrote:
> So if you don't want to allow multiple statements, use PQexecParams et
> al.

That does leave most application authors out in the cold though, since 
they're using a higher level connection manager.

If the maintenance burden isn't terribly high it would be nice to allow 
disabling multiple statements via a GUC.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)



pgsql-hackers by date:

Previous
From: "Rader, David"
Date:
Subject: Re: [HACKERS] [BUGS] Seems bug in postgres_fdw?
Next
From: Jim Nasby
Date:
Subject: Re: [HACKERS] PATCH: Make pg_stop_backup() archive wait optional