RE: Idea to enhance pgbench by more modes to generate data (multi-TXNs, UNNEST, COPY BINARY) - Mailing list pgsql-hackers

From Madyshev Egor
Subject RE: Idea to enhance pgbench by more modes to generate data (multi-TXNs, UNNEST, COPY BINARY)
Date
Msg-id 4a3bfa370a7d48d1965b12572a0de0e5@localhost.localdomain
Whole thread Raw
In response to Re: Idea to enhance pgbench by more modes to generate data (multi-TXNs, UNNEST, COPY BINARY)  (Boris Mironov <boris_mironov@outlook.com>)
Responses Re: Idea to enhance pgbench by more modes to generate data (multi-TXNs, UNNEST, COPY BINARY)
List pgsql-hackers
Hi Boris,

I've finished reviewing the latest v15 version of your patch, everything looks good.
- The patch is applied to the current version of the master branch.
- All check-world tests pass. The patch adds tests for the implemented functionality.
- The code conforms to the PostgreSQL coding style (verified by pgindent).
- The added functionality has been tested and works as expected.
- The added functionality does not violate the existing one.
- Difficult-to-understand code locations are properly commented.
- The documentation has been updated and is correct.

The patch adds two additional data generation modes to pgbench: SELECT unnest on the
server and COPY.. FROM BINARY on the client. As well as a setting that includes
adding data in multitransaction mode. This allows you to positively influence
performance at large --scale=. All this will also make it possible to implement
parallel data loading in several sessions in the future.
The unnest mode will be useful for columnar tables.

All of the above allows me to consider the patch ready for the committer.

I am updating the patch to the Ready for Committer status.

Best regards,
Egor



pgsql-hackers by date:

Previous
From: Greg Sabino Mullane
Date:
Subject: Re: ALTER TABLE: warn when actions do not recurse to partitions
Next
From: Yura Sokolov
Date:
Subject: Re: Why clearing the VM doesn't require registering vm buffer in wal record