git.postgresql.org Git - postgresql.git/commitdiff

diff --git a/src/backend/executor/execPartition.c b/src/backend/executor/execPartition.c

index 901dd435efdfaf3af36dc56873927b30925fdcb7..40e3c076939f126a5d139da55cd43bb51db18a2e 100644 (file)

--- a/src/backend/executor/execPartition.c

+++ b/src/backend/executor/execPartition.c

* Current values of the indexes present in PartitionPruneState count all the

* subplans that would be present before initial pruning was done. If initial

* pruning got rid of some of the subplans, any subsequent pruning passes will

- * will be looking at a different set of target subplans to choose from than

- * those in the pre-initial-pruning set, so the maps in PartitionPruneState

+ * be looking at a different set of target subplans to choose from than those

+ * in the pre-initial-pruning set, so the maps in PartitionPruneState

* containing those indexes must be updated to reflect the new indexes of

* subplans in the post-initial-pruning set.

*/

diff --git a/src/backend/utils/activity/pgstat.c b/src/backend/utils/activity/pgstat.c

index b0ff21b6908a27c01974e4b8eb28007974e907c2..9e3b643a2cd6b080614bfd38ec4ababdf91a7294 100644 (file)

--- a/src/backend/utils/activity/pgstat.c

+++ b/src/backend/utils/activity/pgstat.c

* suggested idle timeout is returned. Currently this is always

* PGSTAT_IDLE_INTERVAL (10000ms). Callers can use the returned time to set up

* a timeout after which to call pgstat_report_stat(true), but are not

- * required to to do so.

+ * required to do so.

*

* Note that this is called only when not within a transaction, so it is fair

* to use transaction stop time as an approximation of current time.

diff --git a/src/backend/utils/activity/pgstat_replslot.c b/src/backend/utils/activity/pgstat_replslot.c

index b77c05ab5fa05b7af7de2aab99b65de7d3443620..2039ac3147fc52b0a2896cdb67dc0fd8fd901020 100644 (file)

--- a/src/backend/utils/activity/pgstat_replslot.c

+++ b/src/backend/utils/activity/pgstat_replslot.c

* storage implementation and the details about individual types of

* statistics.

*

- * Replication slot stats work a bit different than other other

- * variable-numbered stats. Slots do not have oids (so they can be created on

- * physical replicas). Use the slot index as object id while running. However,

- * the slot index can change when restarting. That is addressed by using the

- * name when (de-)serializing. After a restart it is possible for slots to

- * have been dropped while shut down, which is addressed by not restoring

- * stats for slots that cannot be found by name when starting up.

+ * Replication slot stats work a bit different than other variable-numbered

+ * stats. Slots do not have oids (so they can be created on physical

+ * replicas). Use the slot index as object id while running. However, the slot

+ * index can change when restarting. That is addressed by using the name when

+ * (de-)serializing. After a restart it is possible for slots to have been

+ * dropped while shut down, which is addressed by not restoring stats for

+ * slots that cannot be found by name when starting up.

*

* Copyright (c) 2001-2022, PostgreSQL Global Development Group

*

diff --git a/src/test/ssl/t/SSL/Server.pm b/src/test/ssl/t/SSL/Server.pm

index 62f54dcbf1698b8f0b560199911a81f468e07c31..9520578e7d9fa7b192e39091cf6351d2ba322004 100644 (file)

--- a/src/test/ssl/t/SSL/Server.pm

+++ b/src/test/ssl/t/SSL/Server.pm

=item keyfile => B<value>

-The private key to to use. Implementation is SSL backend specific.

+The private key to use. Implementation is SSL backend specific.

=item crlfile => B<value>