MerginMaps / MerginMaps/db-sync
Init with many features can fail with psycopg2.OperationalError
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 53
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
It has been seen in testing that when using a remote PostgreSQL server and a table with many rows, the init (from gpkg) can consistently fail.
Probably related to https://github.com/MerginMaps/db-sync/issues/45
```
Traceback (most recent call last):
File "dbsync_daemon.py", line 216, in
File "dbsync_daemon.py", line 175, in main
File "dbsync.py", line 1450, in dbsync_init
File "dbsync.py", line 1319, in init
File "dbsync.py", line 586, in _set_db_project_comment
psycopg2.OperationalError: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in dbsync.py at init and _set_db_project_comment, where the traceback reports the failure, and reproduce the init from a GeoPackage against a remote PostgreSQL server with many rows. Review the related db-sync issue and determine the cause; done means this initialization no longer fails with psycopg2.OperationalError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100