Skip to content
New issue

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

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

Already on GitHub? # to your account

winnie crashing on pgRouting 3.7.1 /betweennessCentrality/edge_cases.pg:279 #2706

Closed
Tracked by #2710
robe2 opened this issue Dec 24, 2024 · 1 comment · Fixed by #2711
Closed
Tracked by #2710

winnie crashing on pgRouting 3.7.1 /betweennessCentrality/edge_cases.pg:279 #2706

robe2 opened this issue Dec 24, 2024 · 1 comment · Fixed by #2711
Assignees
Labels
Milestone

Comments

@robe2
Copy link
Member

robe2 commented Dec 24, 2024

This might have been going on for a while so have to revisit. It shows green which is misleading hiding the fact it crashes.

No noeed to do anything about it just yet, I'll confirm my crash on my local pc first.

Problem

psql:../../pgtap/max_flow/maxCardinalityMatch/edge_cases.pg:66: WARNING:  pgr_maxCardinalityMatch(text,boolean) deprecated signature on v3.4.0
psql:../../pgtap/max_flow/maxCardinalityMatch/edge_cases.pg:66: WARNING:  pgr_maxCardinalityMatch(text,boolean) deprecated signature on v3.4.0
psql:../../pgtap/max_flow/maxCardinalityMatch/edge_cases.pg:70: WARNING:  pgr_maxCardinalityMatch(text,boolean) deprecated signature on v3.4.0
psql:../../pgtap/max_flow/maxCardinalityMatch/edge_cases.pg:71: WARNING:  pgr_maxCardinalityMatch(text,boolean) deprecated signature on v3.4.0
psql:../../pgtap/metrics/betweennessCentrality/edge_cases.pg:279: server closed the connection unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request.
psql:../../pgtap/metrics/betweennessCentrality/edge_cases.pg:279: fatal: connection to server was lost
psql: error: connection to server at "localhost" (::1), port 20464 failed: server closed the connection unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request.
psql: error: connection to server at "localhost" (::1), port 20464 failed: FATAL:  the database system is in recovery mode

psql: error: connection to server at "localhost" (::1), port 20464 failed: FATAL: the database system is in recovery mode

SELECT version(); 
SELECT postgis_full_version();
SELECT pgr_version();
PostgreSQL 14
PostGIS 3.5.1
3.7.1
@robe2 robe2 added the bug label Dec 24, 2024
@robe2
Copy link
Member Author

robe2 commented Dec 24, 2024

Okay seems to be an issue on at least PostgreSQL 17 too the same the location of crash. PG15 for some reason didn't test so have to investigate that. The others are still processing.

@cvvergara cvvergara added this to the Release 3.7.2 milestone Jan 6, 2025
@cvvergara cvvergara self-assigned this Jan 6, 2025
cvvergara added a commit to cvvergara/pgrouting that referenced this issue Jan 6, 2025
@cvvergara cvvergara mentioned this issue Jan 6, 2025
3 tasks
cvvergara added a commit to cvvergara/pgrouting that referenced this issue Jan 6, 2025
cvvergara added a commit to cvvergara/pgrouting that referenced this issue Jan 6, 2025
cvvergara added a commit to cvvergara/pgrouting that referenced this issue Jan 7, 2025
cvvergara added a commit that referenced this issue Jan 10, 2025
(cherry picked from commit ae34f13)
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants