diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2021-01-30 11:05:15 +0100 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2021-01-30 11:21:32 +0100 |
| commit | 65330622441d7ee08f768c4326825ae903f2595a (patch) | |
| tree | 9aa5e370900f247079bffb2d365cbeb5723532f8 /src/backend/utils/adt/jsonfuncs.c | |
| parent | 6aaaa76bb47db11cd6f567eafa3d1ee81ca59556 (diff) | |
| download | postgresql-65330622441d7ee08f768c4326825ae903f2595a.tar.gz postgresql-65330622441d7ee08f768c4326825ae903f2595a.zip | |
doc: Clarify status of SELECT INTO on reference page
The documentation as well as source code comments weren't entirely
clear whether SELECT INTO was truly deprecated (thus in theory
destined to be removed eventually), or just a less recommended
variant. After discussion, it appears that other implementations also
use SELECT INTO in direct SQL in a way similar to PostgreSQL, so it
seems worth keeping it for compatibility. Update the language in the
documentation to that effect.
Discussion: https://www.postgresql.org/message-id/flat/96dc0df3-e13a-a85d-d045-d6e2c85218da%40enterprisedb.com
Diffstat (limited to 'src/backend/utils/adt/jsonfuncs.c')
0 files changed, 0 insertions, 0 deletions