Init with many features can fail with psycopg2.OperationalError

Open
#176 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
postgresql, python
Domain
databases

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.

Description

bug

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 <module>
  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.
Dominant language
Python
Stars
53
Forks
24
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MerginMaps/db-sync

All issues in MerginMaps/db-sync

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.