Scroll to navigation

PGCOPYDB CLONE(1) pgcopydb PGCOPYDB CLONE(1)

NAME

pgcopydb clone - pgcopydb clone

The main pgcopydb operation is the clone operation, and for historical and user friendlyness reasons three aliases are available that implement the same operation:

pgcopydb


  clone     Clone an entire database from source to target


  fork      Clone an entire database from source to target


  copy-db   Copy an entire database from source to target


PGCOPYDB CLONE

The command pgcopydb clone copies a database from the given source Postgres instance to the target Postgres instance.

pgcopydb clone: Clone an entire database from source to target
usage: pgcopydb clone  --source ... --target ... [ --table-jobs ... --index-jobs ... ]


  --source                   Postgres URI to the source database


  --target                   Postgres URI to the target database


  --dir                      Work directory to use


  --table-jobs               Number of concurrent COPY jobs to run


  --index-jobs               Number of concurrent CREATE INDEX jobs to run


  --split-tables-larger-than Same-table concurrency size threshold


  --drop-if-exists           On the target database, clean-up from a previous run first


  --roles                    Also copy roles found on source to target


  --no-role-passwords        Do not dump passwords for roles


  --no-owner                 Do not set ownership of objects to match the original database


  --no-acl                   Prevent restoration of access privileges (grant/revoke commands).


  --no-comments              Do not output commands to restore comments


  --skip-large-objects       Skip copying large objects (blobs)


  --skip-extensions          Skip restoring extensions


  --skip-collations          Skip restoring collations


  --filters <filename>       Use the filters defined in <filename>


  --restart                  Allow restarting when temp files exist already


  --resume                   Allow resuming operations after a failure


  --not-consistent           Allow taking a new snapshot on the source database


  --snapshot                 Use snapshot obtained with pg_export_snapshot


  --follow                   Implement logical decoding to replay changes


  --plugin                   Output plugin to use (test_decoding, wal2json)


  --slot-name                Use this Postgres replication slot name


  --create-slot              Create the replication slot


  --origin                   Use this Postgres replication origin node name


  --endpos                   Stop replaying changes when reaching this LSN


PGCOPYDB FORK

The command pgcopydb fork copies a database from the given source Postgres instance to the target Postgres instance. This command is an alias to the command pgcopydb clone seen above.

PGCOPYDB COPY-DB

The command pgcopydb copy-db copies a database from the given source Postgres instance to the target Postgres instance. This command is an alias to the command pgcopydb clone seen above, and available for backward compatibility only.

WARNING:

The pgcopydb copy-db command is now deprecated and will get removed from pgcopydb when hitting version 1.0, please upgrade your scripts and integrations.


DESCRIPTION

The pgcopydb clone command implements both a base copy of a source database into a target database and also a full Logical Decoding client for the wal2json logical decoding plugin.

Base copy, or the clone operation

The pgcopydb clone command implements the following steps:

1.
pgcopydb calls into pg_dump to produce the pre-data section and the post-data sections of the dump using Postgres custom format.
2.
pgcopydb gets the list of ordinary and partitioned tables from a catalog query on the source database, and also the list of indexes, and the list of sequences with their current values.

When filtering is used, the list of objects OIDs that are meant to be filtered out is built during this step.

3.
The pre-data section of the dump is restored on the target database using the pg_restore command, creating all the Postgres objects from the source database into the target database.

When filtering is used, the pg_restore --use-list feature is used to filter the list of objects to restore in this step.

4.
Then as many as --table-jobs COPY sub-processes are started to share the workload and COPY the data from the source to the target database one table at a time, in a loop.

A Postgres connection and a SQL query to the Postgres catalog table pg_class is used to get the list of tables with data to copy around, and the reltuples statistic is used to start with the tables with the greatest number of rows first, as an attempt to minimize the copy time.

5.
An auxiliary process loops through all the Large Objects found on the source database and copies its data parts over to the target database, much like pg_dump itself would.

This step is much like pg_dump | pg_restore for large objects data parts, except that there isn't a good way to do just that with the tooling.

6.
As many as --index-jobs CREATE INDEX sub-processes are started to share the workload and build indexes. In order to make sure to start the CREATE INDEX commands only after the COPY operation has completed, a queue mechanism is used. As soon as a table data COPY has completed, all the indexes for the table are queued for processing by the CREATE INDEX sub-processes.

The primary indexes are created as UNIQUE indexes at this stage.

7.
Then the PRIMARY KEY constraints are created USING the just built indexes. This two-steps approach allows the primary key index itself to be created in parallel with other indexes on the same table, avoiding an EXCLUSIVE LOCK while creating the index.
8.
As many as -table-jobs VACUUM ANALYZE sub-processes are started to share the workload. As soon as a table data COPY has completed, the table is queued for processing by the VACUUM ANALYZE sub-processes.
9.
An auxilliary process is loops over the sequences on the source database and for each of them runs a separate query on the source to fetch the last_value and the is_called metadata the same way that pg_dump does.

For each sequence, pgcopydb then calls pg_catalog.setval() on the target database with the information obtained on the source database.

10.
The final stage consists now of running the pg_restore command for the post-data section script for the whole database, and that's where the foreign key constraints and other elements are created.

The post-data script is filtered out using the pg_restore --use-list option so that indexes and primary key constraints already created in steps 6 and 7 are properly skipped now.




Postgres privileges, superuser, and dump and restore

Postgres has a notion of a superuser status that can be assigned to any role in the system, and the default role postgres has this status. From the Role Attributes documentation page we see that:

superuser status:

A database superuser bypasses all permission checks, except the right to log in. This is a dangerous privilege and should not be used carelessly; it is best to do most of your work as a role that is not a superuser. To create a new database superuser, use CREATE ROLE name SUPERUSER. You must do this as a role that is already a superuser.



Some Postgres objects can only be created by superusers, and some read and write operations are only allowed to superuser roles, such as the following non-exclusive list:

  • Reading the pg_authid role password (even when encrypted) is restricted to roles with the superuser status. Reading this catalog table is done when calling pg_dumpall --roles-only so that the dump file can then be used to restore roles including their passwords.

    It is possible to implement a pgcopydb migration that skips the passwords entirely when using the option --no-role-passwords. In that case though authentication might fail until passwords have been setup again correctly.

  • Most of the available Postgres extensions, at least when being written in C, are then only allowed to be created by roles with superuser status.

    When such an extension contains Extension Configuration Tables and has been created with a role having superuser status, then the same superuser status is needed again to pg_dump and pg_restore that extension and its current configuration.




When using pgcopydb it is possible to split your migration in privileged and non-privileged parts, like in the following examples:



 $ coproc ( pgcopydb snapshot )


 # first two commands would use a superuser role to connect


 $ pgcopydb copy roles --source ... --target ...


 $ pgcopydb copy extensions --source ... --target ...


 # now it's possible to use a non-superuser role to connect


 $ pgcopydb clone --skip-extensions --source ... --target ...


 $ kill -TERM ${COPROC_PID}


 $ wait ${COPROC_PID}


In such a script, the calls to pgcopydb copy roles and pgcopydb copy extensions would be done with connection strings that connects with a role having superuser status; and then the call to pgcopydb clone would be done with a non-privileged role, typically the role that owns the source and target databases.

WARNING:

That said, there is currently a limitation in pg_dump that impacts pgcopydb. When an extension with configuration table has been installed as superuser, even the main pgcopydb clone operation has to be done with superuser status.

That's because pg_dump filtering (here, there --exclude-table option) does not apply to extension members, and pg_dump does not provide a mechanism to exclude extensions.



Change Data Capture using Postgres Logical Decoding

When using the --follow option the steps from the pgcopydb follow command are also run concurrently to the main copy. The Change Data Capture is then automatically driven from a prefetch-only phase to the prefetch-and-catchup phase, which is enabled as soon as the base copy is done.

See the command pgcopydb stream sentinel set endpos to remote control the follow parts of the command even while the command is already running.

The command pgcopydb stream cleanup must be used to free resources created to support the change data capture process.

IMPORTANT:

Make sure to read the documentation for pgcopydb follow and the specifics about Logical Replication Restrictions as documented by Postgres.


Change Data Capture Example 1

A simple approach to applying changes after the initial base copy has been done follows:



 $ pgcopydb clone --follow &


 # later when the application is ready to make the switch


 $ pgcopydb stream sentinel set endpos --current


 # later when the migration is finished, clean-up both source and target


 $ pgcopydb stream cleanup


Change Data Capture Example 2

In some cases, it might be necessary to have more control over some of the steps taken here. Given pgcopydb flexibility, it's possible to implement the following steps:

1.
Grab a snapshot from the source database and hold an open Postgres connection for the duration of the base copy.

In case of crash or other problems with the main operations, it's then possible to resume processing of the base copy and the applying of the changes with the same snapshot again.

This step is also implemented when using pgcopydb clone --follow. That said, if the command was interrupted (or crashed), then the snapshot would be lost.

2.
Setup the logical decoding within the snapshot obtained in the previous step, and the replication tracking on the target database.

The following SQL objects are then created:

  • a replication slot on the source database,
  • a pgcopydb.sentinel table on the source database,
  • a replication origin on the target database.



This step is also implemented when using pgcopydb clone --follow. There is no way to implement Change Data Capture with pgcopydb and skip creating those SQL objects.

3.
Start the base copy of the source database, and prefetch logical decoding changes to ensure that we consume from the replication slot and allow the source database server to recycle its WAL files.
4.
Remote control the apply process to stop consuming changes and applying them on the target database.
5.
Re-sync the sequences to their now-current values.

Sequences are not handled by Postgres logical decoding, so extra care needs to be implemented manually here.

IMPORTANT:

The next version of pgcopydb will include that step in the pgcopydb clone --snapshot command automatically, after it stops consuming changes and before the process terminates.


6.
Clean-up the specific resources created for supporting resumability of the whole process (replication slot on the source database, pgcopydb sentinel table on the source database, replication origin on the target database).
7.
Stop holding a snaphot on the source database by stopping the pgcopydb snapshot process left running in the background.



If the command pgcopydb clone --follow fails it's then possible to start it again. It will automatically discover what was done successfully and what needs to be done again because it failed or was interrupted (table copy, index creation, resuming replication slot consuming, resuming applying changes at the right LSN position, etc).

Here is an example implement the previous steps:



 $ pgcopydb snapshot &


 $ pgcopydb stream setup


 $ pgcopydb clone --follow &


 # later when the application is ready to make the switch


 $ pgcopydb stream sentinel set endpos --current


 # when the follow process has terminated, re-sync the sequences


 $ pgcopydb copy sequences


 # later when the migration is finished, clean-up both source and target


 $ pgcopydb stream cleanup


 # now stop holding the snapshot transaction (adjust PID to your environment)


 $ kill %1


OPTIONS

The following options are available to pgcopydb clone:

Connection string to the source Postgres instance. See the Postgres documentation for connection strings for the details. In short both the quoted form "host=... dbname=..." and the URI form postgres://user@host:5432/dbname are supported.
Connection string to the target Postgres instance.
During its normal operations pgcopydb creates a lot of temporary files to track sub-processes progress. Temporary files are created in the directory location given by this option, or defaults to ${TMPDIR}/pgcopydb when the environment variable is set, or then to /tmp/pgcopydb.
How many tables can be processed in parallel.

This limit only applies to the COPY operations, more sub-processes will be running at the same time that this limit while the CREATE INDEX operations are in progress, though then the processes are only waiting for the target Postgres instance to do all the work.

How many indexes can be built in parallel, globally. A good option is to set this option to the count of CPU cores that are available on the Postgres target system, minus some cores that are going to be used for handling the COPY operations.
Allow Same-table Concurrency when processing the source database. This environment variable value is expected to be a byte size, and bytes units B, kB, MB, GB, TB, PB, and EB are known.
When restoring the schema on the target Postgres instance, pgcopydb actually uses pg_restore. When this options is specified, then the following pg_restore options are also used: --clean --if-exists.

This option is useful when the same command is run several times in a row, either to fix a previous mistake or for instance when used in a continuous integration system.

This option causes DROP TABLE and DROP INDEX and other DROP commands to be used. Make sure you understand what you're doing here!

The option --roles add a preliminary step that copies the roles found on the source instance to the target instance. As Postgres roles are global object, they do not exist only within the context of a specific database, so all the roles are copied over when using this option.

The pg_dumpall --roles-only is used to fetch the list of roles from the source database, and this command includes support for passwords. As a result, this operation requires the superuser privileges.

See also pgcopydb copy roles.

Do not dump passwords for roles. When restored, roles will have a null password, and password authentication will always fail until the password is set. Since password values aren't needed when this option is specified, the role information is read from the catalog view pg_roles instead of pg_authid. Therefore, this option also helps if access to pg_authid is restricted by some security policy.
Do not output commands to set ownership of objects to match the original database. By default, pg_restore issues ALTER OWNER or SET SESSION AUTHORIZATION statements to set ownership of created schema elements. These statements will fail unless the initial connection to the database is made by a superuser (or the same user that owns all of the objects in the script). With --no-owner, any user name can be used for the initial connection, and this user will own all the created objects.
Skip copying large objects, also known as blobs, when copying the data from the source database to the target database.
Skip copying extensions from the source database to the target database.

When used, schema that extensions depend-on are also skipped: it is expected that creating needed extensions on the target system is then the responsibility of another command (such as pgcopydb copy extensions), and schemas that extensions depend-on are part of that responsibility.

Because creating extensions require superuser, this allows a multi-steps approach where extensions are dealt with superuser privileges, and then the rest of the pgcopydb operations are done without superuser privileges.

Skip copying collations from the source database to the target database.

In some scenarios the list of collations provided by the Operating System on the source and target system might be different, and a mapping then needs to be manually installed before calling pgcopydb.

Then this option allows pgcopydb to skip over collations and assume all the needed collations have been deployed on the target database already.

See also pgcopydb list collations.

This option allows to exclude table and indexes from the copy operations. See Filtering for details about the expected file format and the filtering options available.
When running the pgcopydb command again, if the work directory already contains information from a previous run, then the command refuses to proceed and delete information that might be used for diagnostics and forensics.

In that case, the --restart option can be used to allow pgcopydb to delete traces from a previous run.

When the pgcopydb command was terminated before completion, either by an interrupt signal (such as C-c or SIGTERM) or because it crashed, it is possible to resume the database migration.

When resuming activity from a previous run, table data that was fully copied over to the target server is not sent again. Table data that was interrupted during the COPY has to be started from scratch even when using --resume: the COPY command in Postgres is transactional and was rolled back.

Same reasonning applies to the CREATE INDEX commands and ALTER TABLE commands that pgcopydb issues, those commands are skipped on a --resume run only if known to have run through to completion on the previous one.

Finally, using --resume requires the use of --not-consistent.

In order to be consistent, pgcopydb exports a Postgres snapshot by calling the pg_export_snapshot() function on the source database server. The snapshot is then re-used in all the connections to the source database server by using the SET TRANSACTION SNAPSHOT command.

Per the Postgres documentation about pg_export_snapshot:

Saves the transaction's current snapshot and returns a text string identifying the snapshot. This string must be passed (outside the database) to clients that want to import the snapshot. The snapshot is available for import only until the end of the transaction that exported it.


Now, when the pgcopydb process was interrupted (or crashed) on a previous run, it is possible to resume operations, but the snapshot that was exported does not exists anymore. The pgcopydb command can only resume operations with a new snapshot, and thus can not ensure consistency of the whole data set, because each run is now using their own snapshot.

Instead of exporting its own snapshot by calling the PostgreSQL function pg_export_snapshot() it is possible for pgcopydb to re-use an already exported snapshot.
When the --follow option is used then pgcopydb implements Change Data Capture as detailed in the manual page for pgcopydb follow in parallel to the main copy database steps.

The replication slot is created using the same snapshot as the main database copy operation, and the changes to the source database are prefetched only during the initial copy, then prefetched and applied in a catchup process.

It is possible to give pgcopydb clone --follow a termination point (the LSN endpos) while the command is running with the command pgcopydb stream sentinel set endpos.

Logical decoding output plugin to use. The default is test_decoding which ships with Postgres core itself, so is probably already available on your source server.

It is possible to use wal2json instead. The support for wal2json is mostly historical in pgcopydb, it should not make a user visible difference whether you use the default test_decoding or wal2json.

Logical decoding slot name to use. Defaults to pgcopydb. which is unfortunate when your use-case involves migrating more than one database from the source server.
Instruct pgcopydb to create the logical replication slot to use.
Logical replication target LSN to use. Automatically stop replication and exit with normal exit status 0 when receiving reaches the specified LSN. If there's a record with LSN exactly equal to lsn, the record will be output.

The --endpos option is not aware of transaction boundaries and may truncate output partway through a transaction. Any partially output transaction will not be consumed and will be replayed again when the slot is next read from. Individual messages are never truncated.

See also documentation for pg_recvlogical.

Logical replication target system needs to track the transactions that have been applied already, so that in case we get disconnected or need to resume operations we can skip already replayed transaction.

Postgres uses a notion of an origin node name as documented in Replication Progress Tracking. This option allows to pick your own node name and defaults to "pgcopydb". Picking a different name is useful in some advanced scenarios like migrating several sources in the same target, where each source should have their own unique origin node name.

Increase current verbosity. The default level of verbosity is INFO. In ascending order pgcopydb knows about the following verbosity levels: FATAL, ERROR, WARN, INFO, NOTICE, DEBUG, TRACE.
Set current verbosity to DEBUG level.
Set current verbosity to TRACE level.
Set current verbosity to ERROR level.

ENVIRONMENT

PGCOPYDB_SOURCE_PGURI

Connection string to the source Postgres instance. When --source is ommitted from the command line, then this environment variable is used.


PGCOPYDB_TARGET_PGURI

Connection string to the target Postgres instance. When --target is ommitted from the command line, then this environment variable is used.


PGCOPYDB_TABLE_JOBS

Number of concurrent jobs allowed to run COPY operations in parallel. When --table-jobs is ommitted from the command line, then this environment variable is used.


PGCOPYDB_INDEX_JOBS

Number of concurrent jobs allowed to run CREATE INDEX operations in parallel. When --index-jobs is ommitted from the command line, then this environment variable is used.


PGCOPYDB_SPLIT_TABLES_LARGER_THAN

Allow Same-table Concurrency when processing the source database. This environment variable value is expected to be a byte size, and bytes units B, kB, MB, GB, TB, PB, and EB are known.

When --split-tables-larger-than is ommitted from the command line, then this environment variable is used.



PGCOPYDB_DROP_IF_EXISTS

When true (or yes, or on, or 1, same input as a Postgres boolean) then pgcopydb uses the pg_restore options --clean --if-exists when creating the schema on the target Postgres instance.


PGCOPYDB_SNAPSHOT

Postgres snapshot identifier to re-use, see also --snapshot.


TMPDIR

The pgcopydb command creates all its work files and directories in ${TMPDIR}/pgcopydb, and defaults to /tmp/pgcopydb.


XDG_DATA_HOME

The standard XDG Base Directory Specification defines several environment variables that allow controling where programs should store their files.
XDG_DATA_HOME defines the base directory relative to which user-specific data files should be stored. If $XDG_DATA_HOME is either not set or empty, a default equal to $HOME/.local/share should be used.


When using Change Data Capture (through --follow option and Postgres logical decoding with wal2json) then pgcopydb pre-fetches changes in JSON files and transform them into SQL files to apply to the target database.

These files are stored at the following location, tried in this order:

1.
when --dir is used, then pgcopydb uses the cdc subdirectory of the --dir location,
2.
when XDG_DATA_HOME is set in the environment, then pgcopydb uses that location,
3.
when neither of the previous settings have been used then pgcopydb defaults to using ${HOME}/.local/share.





EXAMPLES

$ export PGCOPYDB_SOURCE_PGURI="port=54311 host=localhost dbname=pgloader"
$ export PGCOPYDB_TARGET_PGURI="port=54311 dbname=plop"
$ export PGCOPYDB_DROP_IF_EXISTS=on
$ pgcopydb clone --table-jobs 8 --index-jobs 12
13:09:08 81987 INFO  Running pgcopydb version 0.8.21.gacd2795.dirty from "/Applications/Postgres.app/Contents/Versions/12/bin/pgcopydb"
13:09:08 81987 INFO  [SOURCE] Copying database from "postgres://@:/pagila?"
13:09:08 81987 INFO  [TARGET] Copying database into "postgres://@:/plop?"
13:09:08 81987 INFO  Using work dir "/var/folders/d7/zzxmgs9s16gdxxcm0hs0sssw0000gn/T//pgcopydb"
13:09:08 81987 INFO  Exported snapshot "00000003-00076012-1" from the source database
13:09:08 81991 INFO  STEP 1: dump the source database schema (pre/post data)
13:09:08 81991 INFO   /Applications/Postgres.app/Contents/Versions/12/bin/pg_dump -Fc --snapshot 00000003-00076012-1 --section pre-data --file /var/folders/d7/zzxmgs9s16gdxxcm0hs0sssw0000gn/T//pgcopydb/schema/pre.dump 'postgres://@:/pagila?'
13:09:08 81991 INFO   /Applications/Postgres.app/Contents/Versions/12/bin/pg_dump -Fc --snapshot 00000003-00076012-1 --section post-data --file /var/folders/d7/zzxmgs9s16gdxxcm0hs0sssw0000gn/T//pgcopydb/schema/post.dump 'postgres://@:/pagila?'
13:09:08 81991 INFO  STEP 2: restore the pre-data section to the target database
13:09:09 81991 INFO  Listing ordinary tables in source database
13:09:09 81991 INFO  Fetched information for 21 tables, with an estimated total of 46 248 tuples and 3776 kB
13:09:09 81991 INFO  Fetching information for 13 sequences
13:09:09 81991 INFO   /Applications/Postgres.app/Contents/Versions/12/bin/pg_restore --dbname 'postgres://@:/plop?' --single-transaction --clean --if-exists --use-list /var/folders/d7/zzxmgs9s16gdxxcm0hs0sssw0000gn/T//pgcopydb/schema/pre.list /var/folders/d7/zzxmgs9s16gdxxcm0hs0sssw0000gn/T//pgcopydb/schema/pre.dump
13:09:09 81991 INFO  STEP 3: copy data from source to target in sub-processes
13:09:09 81991 INFO  STEP 4: create indexes and constraints in parallel
13:09:09 81991 INFO  STEP 5: vacuum analyze each table
13:09:09 81991 INFO  Now starting 8 processes
13:09:09 81991 INFO  Reset sequences values on the target database
13:09:09 82003 INFO  COPY "public"."rental"
13:09:09 82004 INFO  COPY "public"."film"
13:09:09 82009 INFO  COPY "public"."payment_p2020_04"
13:09:09 82002 INFO  Copying large objects
13:09:09 82007 INFO  COPY "public"."payment_p2020_03"
13:09:09 82010 INFO  COPY "public"."film_actor"
13:09:09 82005 INFO  COPY "public"."inventory"
13:09:09 82014 INFO  COPY "public"."payment_p2020_02"
13:09:09 82012 INFO  COPY "public"."customer"
13:09:09 82009 INFO  Creating 3 indexes for table "public"."payment_p2020_04"
13:09:09 82010 INFO  Creating 2 indexes for table "public"."film_actor"
13:09:09 82007 INFO  Creating 3 indexes for table "public"."payment_p2020_03"
13:09:09 82004 INFO  Creating 5 indexes for table "public"."film"
13:09:09 82005 INFO  Creating 2 indexes for table "public"."inventory"
13:09:09 82033 INFO  VACUUM ANALYZE "public"."payment_p2020_04";
13:09:09 82036 INFO  VACUUM ANALYZE "public"."film_actor";
13:09:09 82039 INFO  VACUUM ANALYZE "public"."payment_p2020_03";
13:09:09 82041 INFO  VACUUM ANALYZE "public"."film";
13:09:09 82043 INFO  VACUUM ANALYZE "public"."inventory";
...
...
...
13:09:09 81991 INFO  STEP 7: restore the post-data section to the target database
13:09:09 81991 INFO   /Applications/Postgres.app/Contents/Versions/12/bin/pg_restore --dbname 'postgres://@:/plop?' --single-transaction --clean --if-exists --use-list /var/folders/d7/zzxmgs9s16gdxxcm0hs0sssw0000gn/T//pgcopydb/schema/post.list /var/folders/d7/zzxmgs9s16gdxxcm0hs0sssw0000gn/T//pgcopydb/schema/post.dump


                                          Step   Connection    Duration   Concurrency


 ---------------------------------------------   ----------  ----------  ------------


                                   Dump Schema       source       355ms             1


                                Prepare Schema       target       135ms             1


 COPY, INDEX, CONSTRAINTS, VACUUM (wall clock)         both       641ms        8 + 12


                             COPY (cumulative)         both       1s598             8


                    Large Objects (cumulative)         both        29ms             1


        CREATE INDEX, CONSTRAINTS (cumulative)       target       4s072            12


                               Finalize Schema       target       366ms             1


 ---------------------------------------------   ----------  ----------  ------------


                     Total Wall Clock Duration         both       1s499        8 + 12


 ---------------------------------------------   ----------  ----------  ------------


AUTHOR

Dimitri Fontaine

COPYRIGHT

2023, Dimitri Fontaine

March 15, 2023 0.11