mirror of
https://github.com/postgres/postgres.git
synced 2025-06-14 18:42:34 +03:00
Login event trigger documentation wordsmithing
Minor wordsmithing on the login trigger documentation and code comments to improve readability, as well as fixing a few small incorrect statements in the comments. Author: Robert Treat <rob@xzilla.net> Discussion: https://postgr.es/m/CAJSLCQ0aMWUh1m6E9YdjeqV61baQ=EhteJX8XOxXg8H_2Lcr0Q@mail.gmail.com
This commit is contained in:
@ -39,10 +39,10 @@
|
||||
<para>
|
||||
The <literal>login</literal> event occurs when an authenticated user logs
|
||||
into the system. Any bug in a trigger procedure for this event may
|
||||
prevent successful login to the system. Such bugs may be fixed by
|
||||
setting <xref linkend="guc-event-triggers"/> is set to <literal>false</literal>
|
||||
either in a connection string or configuration file. Alternative is
|
||||
restarting the system in single-user mode (as event triggers are
|
||||
prevent successful login to the system. Such bugs may be worked around by
|
||||
setting <xref linkend="guc-event-triggers"/> to <literal>false</literal>
|
||||
either in a connection string or configuration file. Alternatively, you can
|
||||
restart the system in single-user mode (as event triggers are
|
||||
disabled in this mode). See the <xref linkend="app-postgres"/> reference
|
||||
page for details about using single-user mode.
|
||||
The <literal>login</literal> event will also fire on standby servers.
|
||||
@ -50,7 +50,7 @@
|
||||
writing anything to the database when running on a standby.
|
||||
Also, it's recommended to avoid long-running queries in
|
||||
<literal>login</literal> event triggers. Note that, for instance,
|
||||
canceling connection in <application>psql</application> wouldn't cancel
|
||||
canceling a connection in <application>psql</application> will not cancel
|
||||
the in-progress <literal>login</literal> trigger.
|
||||
</para>
|
||||
|
||||
|
Reference in New Issue
Block a user