Skip to content

Commit c446edc

Browse files
committed
chore: shorten README.md
1 parent 1c6cf8c commit c446edc

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,16 +4,16 @@
44
[![Coverage Status](https://coveralls.io/repos/github/PostgREST/pg_csv/badge.svg)](https://coveralls.io/github/PostgREST/pg_csv)
55
[![Tests](https://github.com/PostgREST/pg_csv/actions/workflows/ci.yaml/badge.svg)](https://github.com/PostgREST/pg_csv/actions)
66

7-
Postgres has the [COPY .. CSV](https://www.postgresql.org/docs/current/sql-copy.html) command, but `COPY` has problems:
7+
Postgres has CSV support on the [COPY](https://www.postgresql.org/docs/current/sql-copy.html) command, but `COPY` has problems:
88

99
- It uses a special protocol, so it doesn't work with other standard features like [prepared statements](https://www.postgresql.org/docs/current/sql-prepare.html), [pipeline mode](https://www.postgresql.org/docs/current/libpq-pipeline-mode.html#LIBPQ-PIPELINE-USING) or [pgbench](https://www.postgresql.org/docs/current/pgbench.html).
1010
- Is not composable. You can't use COPY inside CTEs, subqueries, view definitions or as function arguments.
1111

12-
`pg_csv` offers flexible CSV processing as a solution to these problems.
12+
`pg_csv` offers flexible CSV processing as a solution.
1313

1414
- Includes a CSV aggregate that composes with SQL expressions.
15-
- Native C extension, almost 2 times faster than SQL queries that try to achieve CSV output (see our [CI results](https://github.com/PostgREST/pg_csv/actions/runs/17367407744)).
16-
- Simple installation, no dependencies except Postgres.
15+
- Native C extension, almost 2 times faster than SQL queries that try to output CSV (see our [CI results](https://github.com/PostgREST/pg_csv/actions/runs/17367407744)).
16+
- No dependencies except Postgres.
1717

1818
## Installation
1919

0 commit comments

Comments
 (0)