All those fixes are already included on HEAD thanks to for example
c96581a and
66bde49, and have gone missing on back-branches.
Author: Alexander Lakhin, Liudmila Mantrova
Discussion: https://postgr.es/m/CAEkD-mDJHV3bhgezu3MUafJLoAKsOOT86+wHukKU8_NeiJYhLQ@mail.gmail.com
Backpatch-through: 9.4
The fields sqlcaid,
- sqlcabc,
+ sqlabc,
sqlerrp, and the remaining elements of
sqlerrd and
sqlwarn currently contain no useful
|
- tcvn_to_utf8
+ windows_1258_to_utf8
WIN1258
UTF8
|
- utf8_to_tcvn
+ utf8_to_windows_1258
UTF8
WIN1258
/*
* Choose where to put the index entries and update unionL and unionR
- * accordingly. Append the entries to either v_spl_left or
- * v_spl_right, and care about the counters.
+ * accordingly. Append the entries to either v->spl_left or
+ * v->spl_right, and care about the counters.
*/
if (my_choice_is_left(unionL, curl, unionR, curr))
It should either be issued when the last string has been sent
to the server using PQputline or when the
last string has been received from the server using
- PGgetline. It must be issued or the server
+ PQgetline. It must be issued or the server
will get out of sync
with the client. Upon return
from this function, the server is ready to receive the next SQL
command. The return value is 0 on successful completion,
If no condition name nor SQLSTATE is specified in a
RAISE EXCEPTION command, the default is to use
- RAISE_EXCEPTION> (P0001>). If no message
+ ERRCODE_RAISE_EXCEPTION> (P0001>). If no message
text is specified, the default is to use the condition name or
SQLSTATE as message text.
INSERT INTO cs_active_job(job_id) VALUES (v_job_id);
BEGIN
- INSERT INTO cs_jobs (job_id, start_stamp) VALUES (v_job_id, sysdate);
+ INSERT INTO cs_jobs (job_id, start_stamp) VALUES (v_job_id, now());
EXCEPTION
WHEN dup_val_on_index THEN NULL; -- don't worry if it already exists
END;
C library, processor, memory information, and so on. In most
cases it is sufficient to report the vendor and version, but do
not assume everyone knows what exactly Debian
- contains or that everyone runs on i386s. If you have
+ contains or that everyone runs on x86_64. If you have
installation problems then information about the toolchain on
your machine (compiler,
make, and so
on) is also necessary.
as described in . This requires
specifying the MSFUNC>, MINVFUNC>,
and MSTYPE> parameters, and optionally
- the MSPACE>, MFINALFUNC>, MFINALFUNC_EXTRA>,
+ the MSSPACE>, MFINALFUNC>, MFINALFUNC_EXTRA>,
and MINITCOND> parameters. Except for MINVFUNC>,
these parameters work like the corresponding simple-aggregate parameters
without M>; they define a separate implementation of the
effectively drops all the privileges assigned directly to the session user
and to the other roles it is a member of, leaving only the privileges
available to the named role. On the other hand, if the session user role
- has the NOINHERITS> attribute, SET ROLE> drops the
+ has the NOINHERIT> attribute, SET ROLE> drops the
privileges assigned directly to the session user and instead acquires the
privileges available to the named role.
localityName (alias L)
stateOrProvinceName (alias ST)
organizationName (alias O)
-organizationUnitName (alias OU)
+organizationalUnitName (alias OU)
title
description
initials
Finally, the PL must be declared with the command
-CREATE TRUSTED PROCEDURAL LANGUAGE language-name
+CREATE TRUSTED PROCEDURAL LANGUAGE language_name
HANDLER handler_function_name
INLINE inline_function_name
VALIDATOR validator_function_name ;