I'm using pg_hashids v1.2.1 and have found that the following code will crash the Postgres Postmaster:
SELECT id_decode(null);
and this in the Postgres logs:
2019-02-24 21:16:51.332 UTC [1] LOG: server process (PID 49322) was terminated by signal 11: Segmentation fault
2019-02-24 21:16:51.332 UTC [1] DETAIL: Failed process was running: SELECT id_decode(null)
2019-02-24 21:16:51.332 UTC [1] LOG: terminating any other active server processes
2019-02-24 21:16:51.333 UTC [49319] WARNING: terminating connection because of crash of another server process
I'm not sure what the correct behaviour ought to be (to return NULL or {0}) but believe an outright crash should be avoidable?
Hi,
I'm using pg_hashids v1.2.1 and have found that the following code will crash the Postgres Postmaster:
and this in the Postgres logs:
I'm not sure what the correct behaviour ought to be (to return NULL or {0}) but believe an outright crash should be avoidable?