hi Sunny, thanks for sharing it. About workers I noticed that even having free workers to be used a single table extraction is slow, would be nice if we could split/paralelize extractions based on chucks and fetch size. For example, considering that I have 20 workers to be used, and only have a single connection to extract a single table, the ideal in my point of view will be having 20 workers in parallel extraction data in this single connection, maybe some logic to get number of rows in table and divide a portion of lines per worker?