Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

m.Marshal(os.Stdout, ev); panic: nil Value #84

Open
remotejob opened this issue Mar 2, 2018 · 4 comments
Open

m.Marshal(os.Stdout, ev); panic: nil Value #84

remotejob opened this issue Mar 2, 2018 · 4 comments

Comments

@remotejob
Copy link

I try reproduce yours example but can't Marshal "event"

but event looks don't carry payload:

schema:"public" table:"notes" op:INSERT id:"2" payload:<fields:<key:"created_at" value:<> > fields:<key:"id" value:<> > fields:<key:"note" value:<> > >

pqs breaks result:

{"schema":"public","table":"notes","op":"INSERT","id":"4","payload":{"created_at":

error: nil Value

@tmc
Copy link
Owner

tmc commented Mar 2, 2018

Interesting. Can you help provide a test data set or script to reproduce this?

@remotejob
Copy link
Author

remotejob commented Mar 2, 2018

I try combat about 2-3 hours without positive result last test: I try reproduce all complete as example

psql (9.5.11, server 9.6.2)

event="&{13292 pqstream_notify {\"schema\" : \"public\", \"table\" : \"notes\", \"op\" : \"INSERT\", \"id\" : \"13\", \"payload\" : {\"id\":13,\"created_at\":\"2018-03-02T08:27:23\",\"note\":\"here is a sample note\"}, \"previous\" : null}}"

event looks correct on server.

I can't figure out how use debug 7001 port ??

I tryed as well:

message, err := m.MarshalToString(ev) if err != nil { return err }

As well don't work :(

test on standard Ubuntu 16.04 psql (9.5.11)

As well don't work :(

@remotejob
Copy link
Author

Question:

Your solution under nasty notify limitation ?

exceeded the 8000 byte notify limit

I mean if our payload will exceed 8000 byte it don't work ??

@tmc
Copy link
Owner

tmc commented Sep 25, 2018

@remotejob the fallback behavior omits the details of the record change (and clients would be expected to fetch in that case).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants