On Thu, December 22, 2005 01:54, Szűcs Gábor wrote:
>> That will not happen for timeouts, however, only for things like
>> misconfigured firewalls, servers that aren't running, password changes,
>> and so on.
>
> forgot intentionally ("mis")configured servers. ;) It's a maintenance
> thing
> for us. Either that, or we should be able to remotely tell the process to
> hangup all pqxx activity until resume is allowed. Making it unable to
> connect makes it understand the situation.
Ah, OK. Graceful shutdown... Nice trick, actually. :)
> I chose not to use the trigger mechanism because I fear mid-transaction
> notifications. I certainly do not want to do that. Just issue LISTENs when
> connected, then doing my work, and check for incoming notifs
> (get_notifs())
> when it's comfortable.
No notifications can come in during a transaction. If they could, from
the server's perspective, what would happen if you issued SQL commands to
handle them asynchronously and then your transaction got rolled back!?
Jeroen
_______________________________________________
Libpqxx-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/libpqxx-general
