Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting a segmentation fault error when loading full table #725

Open
helio-sb opened this issue Jan 9, 2025 · 3 comments
Open

Getting a segmentation fault error when loading full table #725

helio-sb opened this issue Jan 9, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@helio-sb
Copy link

helio-sb commented Jan 9, 2025

What language are you using?

Python

What version are you using?

0.4.0

What database are you using?

PostgreSQL

What dataframe are you using?

Pandas

Can you describe your bug?

I was trying to use connectorX to retrieve data from a table we have running on AWS RDS Postgress instance. We are retrieving the full table in our query. It works great in the QA environment with 100K records in the table , but in the environments where we have 11 Milliion records , I got a segmentation Fault error.

What are the steps to reproduce the behavior?

trying to load a large amount of data .

Database setup if the error only happens on specific data or data type

customerId , phone, email, data_1, data_2, data_3

total : 12 columns - String format

Example query / code
select * from table1
ordered by customer_id

What is the error?

zsh: segmentation fault python3.12 localRun.py

@helio-sb helio-sb added the bug Something isn't working label Jan 9, 2025
@wangxiaoying
Copy link
Contributor

wangxiaoying commented Jan 16, 2025

Hi @helio-sb ,

To narrow down the problem.

  1. Is your data updating (the number of rows in the table is changing) when fetching the data?
  2. Does the seg fault occurs at the beginning or after running for a while?
  3. Are you enabling partitioning (setting the partition_on and partition_num) when the error occurs?
  4. Also, will the error seg fault error stay there if you change the dataframe type to arrow (set the return_type=arrow)?

@helio-sb
Copy link
Author

hey @wangxiaoying , thanks for the reply..
1 . no , no changes in the data
2. running after a while, around 1-2 minutes.
3. no specific partition setting, just default options.
4. I will give a try and let you know the results

@wangxiaoying
Copy link
Contributor

hey @wangxiaoying , thanks for the reply.. 1 . no , no changes in the data 2. running after a while, around 1-2 minutes. 3. no specific partition setting, just default options. 4. I will give a try and let you know the results

Thank you! Also, it would be great if you can also test on an older version like pip install connectorx==0.3.4a3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants