diff options
Diffstat (limited to 'doc/src/sgml')
| -rw-r--r-- | doc/src/sgml/config.sgml | 36 | ||||
| -rw-r--r-- | doc/src/sgml/libpq.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/monitoring.sgml | 9 | ||||
| -rw-r--r-- | doc/src/sgml/ref/explain.sgml | 3 | ||||
| -rw-r--r-- | doc/src/sgml/ref/psql-ref.sgml | 11 | ||||
| -rw-r--r-- | doc/src/sgml/spi.sgml | 6 |
6 files changed, 44 insertions, 23 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 0a2a8b49fdb..06d1e4403b5 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -5924,24 +5924,24 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class=" </para> <para> - Random access to mechanical disk storage is normally much more expensive - than four times sequential access. However, a lower default is used - (4.0) because the majority of random accesses to disk, such as indexed - reads, are assumed to be in cache. The default value can be thought of - as modeling random access as 40 times slower than sequential, while - expecting 90% of random reads to be cached. - </para> - - <para> - If you believe a 90% cache rate is an incorrect assumption - for your workload, you can increase random_page_cost to better - reflect the true cost of random storage reads. Correspondingly, - if your data is likely to be completely in cache, such as when - the database is smaller than the total server memory, decreasing - random_page_cost can be appropriate. Storage that has a low random - read cost relative to sequential, e.g., solid-state drives, might - also be better modeled with a lower value for random_page_cost, - e.g., <literal>1.1</literal>. + Random access to durable storage is normally much more expensive + than four times sequential access. However, a lower default is + used (4.0) because the majority of random accesses to storage, + such as indexed reads, are assumed to be in cache. Also, the + latency of network-attached storage tends to reduce the relative + overhead of random access. + </para> + + <para> + If you believe caching is less frequent than the default + value reflects, and network latency is minimal, you can increase + random_page_cost to better reflect the true cost of random storage + reads. Storage that has a higher random read cost relative to + sequential, like magnetic disks, might also be better modeled with + a higher value for random_page_cost. Correspondingly, if your data + is likely to be completely in cache, such as when the database + is smaller than the total server memory, or network latency is + high, decreasing random_page_cost might be appropriate. </para> <tip> diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 5bf59a19855..e76da383714 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -2220,7 +2220,7 @@ postgresql://%2Fvar%2Flib%2Fpostgresql/dbname server does not support the protocol version requested by the client, the connection is automatically downgraded to a lower minor protocol version that the server supports. After the connection attempt has - completed you can use <xref linkend="libpq-PQprotocolVersion"/> to + completed you can use <xref linkend="libpq-PQfullProtocolVersion"/> to find out which exact protocol version was negotiated. </para> diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index d5f0fb7ba7c..f3bf527d5b4 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -3325,6 +3325,15 @@ description | Waiting for a newly initialized WAL file to reach durable storage <row> <entry role="catalog_table_entry"><para role="column_definition"> + <structfield>wal_fpi_bytes</structfield> <type>numeric</type> + </para> + <para> + Total amount of WAL full page images in bytes + </para></entry> + </row> + + <row> + <entry role="catalog_table_entry"><para role="column_definition"> <structfield>wal_buffers_full</structfield> <type>bigint</type> </para> <para> diff --git a/doc/src/sgml/ref/explain.sgml b/doc/src/sgml/ref/explain.sgml index 6dda680aa0d..7dee77fd366 100644 --- a/doc/src/sgml/ref/explain.sgml +++ b/doc/src/sgml/ref/explain.sgml @@ -241,7 +241,8 @@ ROLLBACK; <para> Include information on WAL record generation. Specifically, include the number of records, number of full page images (fpi), the amount of WAL - generated in bytes and the number of times the WAL buffers became full. + generated in bytes, the amount of full page images generated in bytes, + and the number of times the WAL buffers became full. In text format, only non-zero values are printed. This parameter may only be used when <literal>ANALYZE</literal> is also enabled. It defaults to <literal>FALSE</literal>. diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index 1a339600bc4..84683f62b1c 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -4974,6 +4974,17 @@ testdb=> <userinput>INSERT INTO my_table VALUES (:'content');</userinput> </listitem> </varlistentry> + <varlistentry id="app-psql-prompting-S"> + <term><literal>%S</literal></term> + <listitem> + <para> + The current value of <xref linkend="guc-search-path"/>, or + <literal>?</literal> if connected to a server running + <productname>PostgreSQL</productname> 17 or older. + </para> + </listitem> + </varlistentry> + <varlistentry id="app-psql-prompting-s"> <term><literal>%s</literal></term> <listitem><para>The name of the service.</para></listitem> diff --git a/doc/src/sgml/spi.sgml b/doc/src/sgml/spi.sgml index 7e2f2df965d..e30d0962ae7 100644 --- a/doc/src/sgml/spi.sgml +++ b/doc/src/sgml/spi.sgml @@ -846,7 +846,7 @@ int SPI_execute_extended(const char *<parameter>command</parameter>, <synopsis> int SPI_execute_with_args(const char *<parameter>command</parameter>, int <parameter>nargs</parameter>, Oid *<parameter>argtypes</parameter>, - Datum *<parameter>values</parameter>, const char *<parameter>nulls</parameter>, + const Datum *<parameter>values</parameter>, const char *<parameter>nulls</parameter>, bool <parameter>read_only</parameter>, long <parameter>count</parameter>) </synopsis> </refsynopsisdiv> @@ -1671,7 +1671,7 @@ bool SPI_is_cursor_plan(SPIPlanPtr <parameter>plan</parameter>) <refsynopsisdiv> <synopsis> -int SPI_execute_plan(SPIPlanPtr <parameter>plan</parameter>, Datum * <parameter>values</parameter>, const char * <parameter>nulls</parameter>, +int SPI_execute_plan(SPIPlanPtr <parameter>plan</parameter>, const Datum * <parameter>values</parameter>, const char * <parameter>nulls</parameter>, bool <parameter>read_only</parameter>, long <parameter>count</parameter>) </synopsis> </refsynopsisdiv> @@ -2317,7 +2317,7 @@ Portal SPI_cursor_open(const char * <parameter>name</parameter>, SPIPlanPtr <par Portal SPI_cursor_open_with_args(const char *<parameter>name</parameter>, const char *<parameter>command</parameter>, int <parameter>nargs</parameter>, Oid *<parameter>argtypes</parameter>, - Datum *<parameter>values</parameter>, const char *<parameter>nulls</parameter>, + const Datum *<parameter>values</parameter>, const char *<parameter>nulls</parameter>, bool <parameter>read_only</parameter>, int <parameter>cursorOptions</parameter>) </synopsis> </refsynopsisdiv> |