On 22/05/10 12:01, Craig Ringer wrote:
On 21/05/2010 10:35 PM, Magnus Hagander wrote:
>>
Unfortunately, I don't think this is something we can fix as a bugfix
- it'll be a pretty clear change of behaviour, so I think it's
something we will need to push back for a full release, which would
mean
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.
Qualquer versao que instalo da erro conforme abaixo :
An error ocurred executing the Microsoft VC++ runtime installer, poderiam me
dar uma dica de solução ?
Obrigado
_
DIVIRTA SEUS AMIGOS
2010/5/22 Tom Molesworth :
> 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
On Sat, May 22, 2010 at 5:56 PM, Tom Molesworth wrote:
> Surely this is normal, expected behaviour - exactly the same as you'd get
> from the mysql commandline client, for example?
> Note that I'm not the original submitter - so I could be missing the point
> entirely here!
If you were missing
Hi Joshua,
On 23/05/10 00:45, Joshua Tolley wrote:
2010/5/22 Tom Molesworth:
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
