upstream/postgresql
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2026-02-17 01:31:07 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
postgresql/src/interfaces/ecpg
History
Thomas Munro 68a4b58eca Remove --disable-thread-safety and related code. 
All supported computers have either POSIX or Windows threads, and we no
longer have any automated testing of --disable-thread-safety.  We define
a vestigial ENABLE_THREAD_SAFETY macro to 1 in ecpg_config.h in case it
is useful, but we no longer test it anywhere in PostgreSQL code, and
associated dead code paths are removed.

The Meson and perl-based Windows build scripts never had an equivalent
build option.

Reviewed-by: Andres Freund <andres@anarazel.de>
Reviewed-by: Peter Eisentraut <peter@eisentraut.org>
Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Discussion: https://postgr.es/m/CA%2BhUKGLtmexrpMtxBRLCVePqV_dtWG-ZsEbyPrYc%2BNBB2TkNsw%40mail.gmail.com
2023-07-12 08:20:43 +12:00
..
compatlib pkg-config Requires.private entries should be comma-separated 2023-03-16 07:37:38 +01:00
ecpglib Remove --disable-thread-safety and related code. 2023-07-12 08:20:43 +12:00
include Remove --disable-thread-safety and related code. 2023-07-12 08:20:43 +12:00
pgtypeslib Pre-beta mechanical code beautification. 2023-05-19 17:24:48 -04:00
preproc Handle \v as a whitespace character in parsers 2023-07-06 08:16:24 +09:00
test Remove --disable-thread-safety and related code. 2023-07-12 08:20:43 +12:00
Makefile Add a temp-install prerequisite to src/interfaces/ecpg "checktcp". 2022-04-16 17:43:54 -07:00
meson.build Update copyright for 2023 2023-01-02 15:00:37 -05:00
README.dynSQL Fix whitespace issues found by git diff --check, add gitattributes 2013-11-10 14:48:29 -05:00

README.dynSQL 

src/interfaces/ecpg/README.dynSQL

descriptor statements have the following shortcomings

- input descriptors (USING DESCRIPTOR <name>) are not supported

  Reason: to fully support dynamic SQL the frontend/backend communication
          should change to recognize input parameters.
          Since this is not likely to happen in the near future and you
          can cover the same functionality with the existing infrastructure
          (using s[n]printf), I'll leave the work to someone else.