mirror of
https://github.com/postgres/postgres.git
synced 2025-04-25 21:42:33 +03:00
Docs: make prose discussion match the ordering of Table 9-58.
The "Session Information Functions" table seems to be sorted mostly alphabetically (although it's not perfect), which would be all right if it didn't lead to some related functions being described in a pretty nonintuitive order. Also, the prose discussions after the table were in an order that hardly matched the table at all. Rearrange to make things a bit easier to follow.
This commit is contained in:
parent
c7a1c5a6b6
commit
64a169d131
@ -15002,6 +15002,12 @@ SELECT * FROM pg_ls_dir('.') WITH ORDINALITY AS t(ls,n);
|
||||
<entry>configuration load time</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry><literal><function>pg_my_temp_schema()</function></literal></entry>
|
||||
<entry><type>oid</type></entry>
|
||||
<entry>OID of session's temporary schema, or 0 if none</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry><literal><function>pg_is_other_temp_schema(<type>oid</type>)</function></literal></entry>
|
||||
<entry><type>boolean</type></entry>
|
||||
@ -15020,12 +15026,6 @@ SELECT * FROM pg_ls_dir('.') WITH ORDINALITY AS t(ls,n);
|
||||
<entry>fraction of the asynchronous notification queue currently occupied (0-1)</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry><literal><function>pg_my_temp_schema()</function></literal></entry>
|
||||
<entry><type>oid</type></entry>
|
||||
<entry>OID of session's temporary schema, or 0 if none</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry><literal><function>pg_postmaster_start_time()</function></literal></entry>
|
||||
<entry><type>timestamp with time zone</type></entry>
|
||||
@ -15156,25 +15156,6 @@ SET search_path TO <replaceable>schema</> <optional>, <replaceable>schema</>, ..
|
||||
</para>
|
||||
</note>
|
||||
|
||||
<indexterm>
|
||||
<primary>pg_listening_channels</primary>
|
||||
</indexterm>
|
||||
|
||||
<indexterm>
|
||||
<primary>pg_notification_queue_usage</primary>
|
||||
</indexterm>
|
||||
|
||||
<para>
|
||||
<function>pg_listening_channels</function> returns a set of names of
|
||||
asynchronous notification channels that the current session is listening
|
||||
to. <function>pg_notification_queue_usage</function> returns the
|
||||
fraction of the total available space for notifications currently
|
||||
occupied by notifications that are waiting to be processed, as a
|
||||
<type>double</type> in the range 0-1.
|
||||
See <xref linkend="sql-listen"> and <xref linkend="sql-notify">
|
||||
for more information.
|
||||
</para>
|
||||
|
||||
<indexterm>
|
||||
<primary>inet_client_addr</primary>
|
||||
</indexterm>
|
||||
@ -15202,6 +15183,20 @@ SET search_path TO <replaceable>schema</> <optional>, <replaceable>schema</>, ..
|
||||
Unix-domain socket.
|
||||
</para>
|
||||
|
||||
<indexterm>
|
||||
<primary>pg_conf_load_time</primary>
|
||||
</indexterm>
|
||||
|
||||
<para>
|
||||
<function>pg_conf_load_time</function> returns the
|
||||
<type>timestamp with time zone</type> when the
|
||||
server configuration files were last loaded.
|
||||
(If the current session was alive at the time, this will be the time
|
||||
when the session itself re-read the configuration files, so the
|
||||
reading will vary a little in different sessions. Otherwise it is
|
||||
the time when the postmaster process re-read the configuration files.)
|
||||
</para>
|
||||
|
||||
<indexterm>
|
||||
<primary>pg_my_temp_schema</primary>
|
||||
</indexterm>
|
||||
@ -15220,6 +15215,25 @@ SET search_path TO <replaceable>schema</> <optional>, <replaceable>schema</>, ..
|
||||
tables from a catalog display.)
|
||||
</para>
|
||||
|
||||
<indexterm>
|
||||
<primary>pg_listening_channels</primary>
|
||||
</indexterm>
|
||||
|
||||
<indexterm>
|
||||
<primary>pg_notification_queue_usage</primary>
|
||||
</indexterm>
|
||||
|
||||
<para>
|
||||
<function>pg_listening_channels</function> returns a set of names of
|
||||
asynchronous notification channels that the current session is listening
|
||||
to. <function>pg_notification_queue_usage</function> returns the
|
||||
fraction of the total available space for notifications currently
|
||||
occupied by notifications that are waiting to be processed, as a
|
||||
<type>double</type> in the range 0-1.
|
||||
See <xref linkend="sql-listen"> and <xref linkend="sql-notify">
|
||||
for more information.
|
||||
</para>
|
||||
|
||||
<indexterm>
|
||||
<primary>pg_postmaster_start_time</primary>
|
||||
</indexterm>
|
||||
@ -15230,20 +15244,6 @@ SET search_path TO <replaceable>schema</> <optional>, <replaceable>schema</>, ..
|
||||
server started.
|
||||
</para>
|
||||
|
||||
<indexterm>
|
||||
<primary>pg_conf_load_time</primary>
|
||||
</indexterm>
|
||||
|
||||
<para>
|
||||
<function>pg_conf_load_time</function> returns the
|
||||
<type>timestamp with time zone</type> when the
|
||||
server configuration files were last loaded.
|
||||
(If the current session was alive at the time, this will be the time
|
||||
when the session itself re-read the configuration files, so the
|
||||
reading will vary a little in different sessions. Otherwise it is
|
||||
the time when the postmaster process re-read the configuration files.)
|
||||
</para>
|
||||
|
||||
<indexterm>
|
||||
<primary>version</primary>
|
||||
</indexterm>
|
||||
|
Loading…
x
Reference in New Issue
Block a user