[Pgpool-general] NOTIFY/LISTEN forwarding?

[Chad Robinson]

Tatsuo Ishii wrote:
>>I'm playing around with version 2.4, and am having a problem with the NOTIFY 
>>feature of Postgres. When I LISTEN, my entry shows up in pg_listeners, so 
>>pgpool is clearly passing that through to the server. But NOTIFY commands 
>>don't seem to make it back to the client. If I send a bunch of them I'll 
>>sporadically receive one or two, especially if I kill and restart the client 
>>(and it connects to the same pgpool PID) but this is sporadic.
>>
>>Is this a bug, or just something pgpool isn't designed to do yet? I see some 
>>NoticeResponse and similar functions in the code, but I don't know if this is 
>>meant for real usage yet.
>>
>>Anything I can do to analyze this further? I'm no stranger to C but I'm very 
>>new to Postgres, so be gentle.
> 
> 
> I did some testings on pgpool 2.5/PostgreSQL 8.0 combo without
> successing to reproduce your problem. Can you tell me how to
> reproduce?
> 
> The only downside of pgpool regarding LISTEN/NOTIFY is if someone
> issues LISTEN and quit the session without listening the notification,
> other guy who accidentaly reuses the connection might get a
> notification. Apparently this is not your case though.

Thanks for responding, but I don't know what more to tell you. I'm running 
Postgres 8.0.1 and pgpool 2.4, as installed by Gentoo's package management 
system. If I directly connect to Postgres, the client receives notifications 
immediately. If I connect to pgpool, it receives them sporadically or not at all.

I did see the behavior you mention, about later clients seeing NOTIFY messages 
intended for earlier clients, but for testing I'm just working with a 
single-client case.

Anyway, unless you care for other reasons, don't worry about it. I created a 
notification interface through another service my application talks to, and 
pgpool's query functions work just fine, so I'm all set for now.

Thanks,
Chad