> > That's a tough one. Why are elog(NOTICE) being sent? Is there a way to
> > buffer those instead?
>
> I thought about that, but gave it up when I realized that it doesn't
> offer a solution to the elog(ERROR) case. The only way not to choke
> for elog(ERROR) is not to start sending the data message until you've
> constructed it completely --- or to have a way of aborting the partially
> sent message, which is feasible for COPY OUT but not really practical
> for SELECT data messages.
>
I think a NOTICE, could be handeled differently than ERROR, since by
definition a NOTICE won't "disturb" the current transaction, while an
ERROR will do an automatic rollback. So I think the ERROR case should
stop transmission to the client immediately and then send the ERROR.
This happens with other DBMS's e.g when a lock timeout has occurred,
or the good old "Snapshot too old" happens. (unload files will be half
finished).
The NOTICE could probably be buffered until the end of current data.
Andreas
