Re: psql or pgbouncer bug?

2010/5/22 Tom Molesworth <tom(at)audioboundary(dot)com>:
> Hi Jakub,
>
> On 21/05/10 16:19, Jakub Ouhrabka wrote:
>>
>> can anyone tell me how this could happen, please?
>>
>> database=# begin; update table set col = 100;
>> server closed the connection unexpectedly
>>       This probably means the server terminated abnormally
>>       before or while processing the request.
>> The connection to the server was lost. Attempting reset: Succeeded.
>> UPDATE 153
>> database=# ROLLBACK ;
>> WARNING:  there is no transaction in progress
>> ROLLBACK

<snip>

> Seems to be trivially easy to reproduce by connecting via psql, then killing
> that connection before issuing the 'begin; update' sequence (against
> postgres directly, no pgbouncer needed). If anything, it's an issue with
> psql settings? Maybe it should stop on connection drop rather than
> attempting reconnect and continuing with further statements.

Does PostgreSQL log anything more detailed? What if you update some
other table similarly? It looks like some sort of data corruption on
the table you're updating.

--
Joshua Tolley / eggyknap
End Point Corporation