# pgloader 3: A planned Common Lisp rewrite with parallel loading and additional data sources

DevFeed: [pgloader 3: A planned Common Lisp rewrite with parallel loading and additional data sources](<https://devfeed.tech/articles/pgloader-what-s-next-34490.md>)

Original publisher: [Read original article](<https://tapoueh.org/blog/2013/01/pgloader-whats-next/>)

Author: Dimitri Fontaine PostgreSQL Major Contributor; Author

Published: 2013-01-28T09:48:00Z

Content type: opinion

Language: en

Sources: [Dimitri Fontaine](<https://devfeed.tech/sources/dimitri-fontaine.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Lisp](<https://devfeed.tech/topics/lisp.md>), [MySQL](<https://devfeed.tech/topics/mysql.md>), [migration](<https://devfeed.tech/topics/migration.md>), [parallel](<https://devfeed.tech/topics/parallel.md>), [Python](<https://devfeed.tech/topics/python.md>)

Tags: [lisp](<https://devfeed.tech/tags/lisp.md>), [migration](<https://devfeed.tech/tags/migration.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [parallel](<https://devfeed.tech/tags/parallel.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [programming](<https://devfeed.tech/tags/programming.md>), [python](<https://devfeed.tech/tags/python.md>)

## AI overview

The article discusses plans for pgloader 3, including a Common Lisp implementation intended to improve loading performance, support real parallel processing, and fetch data from sources such as MySQL, HTTP, and S3. It also notes that existing Python reformatting modules would need to be ported.

## Source excerpt

pgloader is a tool to help loading data into PostgreSQL, adding some error management to the COPY command. COPY is the fast way of loading data into PostgreSQL and is transaction safe. That means that if a single error appears within your bulk of data, you will have loaded none of it. pgloader will submit the data again in smaller chunks until it's able to isolate the bad from the good, and then the good is loaded in.