On Wed, Mar 2, 2011 at 9:58 AM, Dimitri Fontaine <dimi...@2ndquadrant.fr> wrote: > Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> writes: >> To achieve the effect Fujii is looking for, we would have to silently drop >> the connection. That would correctly leave the client not knowing whether >> the transaction committed or not. > > +1 > >>> It might be reasonable to COMMIT but also issue a warning message, or >>> to just close the connection without telling the client what happened, >>> but sending an error seems poor. >> >> Yeah, I guess that would work too, if the client knows to watch out for >> those warnings. > > -1
yeah, unless by warning, you meant 'error'. merlin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
