Alfred Perlstein wrote:
> Whoa whoa... It's a bit more complicated than you think, there's a lot
> of state that gets put into libpq,
I don't think this has anything to do with libpq. This has got to do
with
psql's reading of commands _before_ they get shoved into libpq. As such
it shouldn't be that dangerous.
> i guess the simplest way would be
> to do so and also cancel the transaction, but a simple longjump won't
> work reliably and you'd also have to take very careful steps to make
> sure you handle everything _just right_ from a signal context.
>
> I'd rather have the inconvience of psql exiting than a not entirely
> thought out mechanism for doing this properly potentially having psql
> run amok on my database. :)
>
> --
> -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]
>
> ************
