"Weerts, Jan" <[EMAIL PROTECTED]> writes:
> Scott Marlowe wrote:
>> Can you get set of fields in that row to uniquely identify it by?
>>
>> If so, see if you can update that column to something else and
>> continue
> The only way would be to update by primarykey. But since the
> select on the pr
On Thu, 2006-07-06 at 17:30, Weerts, Jan wrote:
> Scott Marlowe wrote:
> > On Thu, 2006-07-06 at 16:36, Weerts, Jan wrote:
> >> Hi all!
> >>
> >> This was 8.1.3 and now is 8.1.4 running on Debian Sarge, locally
> >> compiled without any fancy options.
> >
> >>
> >> While the first answer seems m
Scott Marlowe wrote:
> On Thu, 2006-07-06 at 16:36, Weerts, Jan wrote:
>> Hi all!
>>
>> This was 8.1.3 and now is 8.1.4 running on Debian Sarge, locally
>> compiled without any fancy options.
>
>>
>> While the first answer seems much more valid (the primarkey is
>> an artificially created number
On Thu, 2006-07-06 at 16:36, Weerts, Jan wrote:
> Hi all!
>
> This was 8.1.3 and now is 8.1.4 running on Debian Sarge, locally
> compiled without any fancy options.
>
> While the first answer seems much more valid (the primarkey is
> an artificially created number), the second answer seems to
>
Hi all!
This was 8.1.3 and now is 8.1.4 running on Debian Sarge, locally
compiled without any fancy options.
Since Tuesday we experience strange diconnects from our database
used as a source code respository for the developers.
First indicators of trouble are log lines like
:ERROR: invalid mem
