mirror of
https://github.com/postgres/postgres.git
synced 2025-06-11 20:28:21 +03:00
Fix inconsistencies and typos in the tree, take 10
This addresses some issues with unnecessary code comments, fixes various typos in docs and comments, and removes some orphaned structures and definitions. Author: Alexander Lakhin Discussion: https://postgr.es/m/9aabc775-5494-b372-8bcb-4dfc0bd37c68@gmail.com
This commit is contained in:
@ -5011,7 +5011,7 @@ struct
|
||||
|
||||
<para>
|
||||
The fields <structfield>sqlcaid</structfield>,
|
||||
<structfield>sqlcabc</structfield>,
|
||||
<structfield>sqlabc</structfield>,
|
||||
<structfield>sqlerrp</structfield>, and the remaining elements of
|
||||
<structfield>sqlerrd</structfield> and
|
||||
<structfield>sqlwarn</structfield> currently contain no useful
|
||||
|
@ -3740,9 +3740,9 @@ RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;
|
||||
<para>
|
||||
If no condition name nor SQLSTATE is specified in a
|
||||
<command>RAISE EXCEPTION</command> command, the default is to use
|
||||
<literal>RAISE_EXCEPTION</literal> (<literal>P0001</literal>). If no message
|
||||
text is specified, the default is to use the condition name or
|
||||
SQLSTATE as message text.
|
||||
<literal>ERRCODE_RAISE_EXCEPTION</literal> (<literal>P0001</literal>).
|
||||
If no message text is specified, the default is to use the condition
|
||||
name or SQLSTATE as message text.
|
||||
</para>
|
||||
|
||||
<note>
|
||||
@ -5626,7 +5626,7 @@ BEGIN
|
||||
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;
|
||||
|
@ -884,7 +884,7 @@ BETTER: unrecognized node type: 42
|
||||
features can be used, if a fallback is provided.
|
||||
</para>
|
||||
<para>
|
||||
For example <literal>_StaticAssert()</literal> and
|
||||
For example <literal>_Static_assert()</literal> and
|
||||
<literal>__builtin_constant_p</literal> are currently used, even though
|
||||
they are from newer revisions of the C standard and a
|
||||
<productname>GCC</productname> extension respectively. If not available
|
||||
|
Reference in New Issue
Block a user