vitaly-t / pg-promise

PostgreSQL interface for Node.js
https://vitaly-t.github.io/pg-promise
MIT License
3.45k stars 217 forks source link

Notification only fires once. #740

Closed pnunn closed 4 years ago

pnunn commented 4 years ago

Expected behavior

Notification is received each time a row is added.

Actual behavior

I get the first notification, then nothing.

Steps to reproduce

Uses the example code under 'robust listeners' connected to the my notification. If I run the listen blah command in phAdmin4 I get the correct notification each time.

Environment

Output is: Successful Initial Connection Received Payload: {"settlementdate":"2020-07-13T20:05:00","runno":1,"duid":"BOCORWF1","tradetype":0,"dispatchinterval":20200713193,"intervention":0,"connectionpointid":"NCMA3B","dispatchmode":0,"agcstatus":0,"initialmw":0.00000,"totalcleared":0.77200,"rampdownrate":180.00000,"rampuprate":720.00000,"lower5min":0.00000,"lower60sec":0.00000,"lower6sec":0.00000,"raise5min":0.00000,"raise60sec":0.00000,"raise6sec":0.00000,"downepf":null,"upepf":null,"marginal5minvalue":null,"marginal60secvalue":null,"marginal6secvalue":null,"marginalvalue":null,"violation5mindegree":null,"violation60secdegree":null,"violation6secdegree":null,"violationdegree":null,"lastchanged":"2020-07-13T20:00:04","lowerreg":0.00000,"raisereg":0.00000,"availability":0.77200,"raise6secflags":0,"raise60secflags":0,"raise5minflags":0,"raiseregflags":0,"lower6secflags":0,"lower60secflags":0,"lower5minflags":0,"lowerregflags":0,"raiseregavailability":0.00000,"raiseregenablementmax":0.00000,"raiseregenablementmin":0.00000,"lowerregavailability":0.00000,"lowerregenablementmax":0.00000,"lowerregenablementmin":0.00000,"raise6secactualavailability":0.000000,"raise60secactualavailability":0.000000,"raise5minactualavailability":0.000000,"raiseregactualavailability":0.000000,"lower6secactualavailability":0.000000,"lower60secactualavailability":0.000000,"lower5minactualavailability":0.000000,"lowerregactualavailability":0.000000,"semidispatchcap":0}

Then nothing when the next row is inserted.

pnunn commented 4 years ago

I take it back.. It must be an issue with the vpn. Running the code on the same server as the DB and there are no issues at all.

Thanks for your work.