Hello,
1) I can perform a query on the rows that I am trying to update. I have
also successfully updated rows before in the same table and also after.
2) I have no reason to believe that the filesystem got corrupted. I have
started a scan before you asked the question wondering if it could be
the problem. So far, no problem has been found.
3) I have an antivirus running, but again this antivirus has been
running for months and I have worked on postgresql also for months.
There has been an update yesterday to that antivirus, but I don't think
it had an impact.
4) The disk space is not a problem with more than 160GB free.
I tried also in the meantime to run a vacuum, and I got some messages
that the indexes had a problem and it was working to fix it. It crashed.
I restarted my pc and could perform the vacuum just fine afterwards.
Richard Huxton wrote:
> Emilie Laffray wrote:
>
>> Hello,
>>
>> I am sending this email since I am hitting a snag with postgresql. I
>> am currently running the following version of postgresql:
>> Postgresql 8.3.5 on Windows XP Pro 32bits
>>
>> I am getting a crash whenever I try to perform an update on some rows.
>> More precisely, I have recently imported a dataset and managed to work
>> through it easily. However, when performing one update I am getting
>> the following error:
>>
>> GMT PANIC: could not write to log file 40, segment 44 at offset
>> 8929280, length 1744896: Invalid argument
>>
>
> 1. Can you run any other queries
> a. A SELECT
> b. A different UPDATE
>
> 2. Do you have any reason to think the filesystem may have become corrupted?
>
> 3. Do you have an antivirus scanner that might be interfering with
> PostgreSQL? That frequently causes strange problems.
>
>
>