Bruce Momjian writes:
> Qingqing Zhou wrote:
>> Things could get worse because the whole database cluster may stop working
>> and waiting for the buffer the bgwriter is working on, but bgwriter is
>> waiting for (by the deadloop in pgunlink) those postgres'es to move on (so
>> that they could clos
Interesting. Are you sure all those processes were using our standard
flags? Seems unusual and you are right, it shouldn't be happening.
---
Qingqing Zhou wrote:
>
> ""Magnus Hagander"" <[EMAIL PROTECTED]> writes
> >
> > I
""Magnus Hagander"" <[EMAIL PROTECTED]> writes
>
> I suggest you try using Process Explorer from www.sysinternals.com to
> figure out who has the file open. Most of the time it should be able to
> tell you exactly who has locked the file - at least as long as it's done
> from userspace. I'm not 10
Qingqing wrote:
> There were several reports of "unable to read/write" on Pg8.0.x win32
> port:
>
> http://archives.postgresql.org/pgsql-bugs/2005-02/msg00181.php
>
> I encounter this several times and finally I catch the GetLastError()
> number. It is
>
> 32, ERROR_SHARING_VIOLATION
> T
""Magnus Hagander"" <[EMAIL PROTECTED]> writes
>
> I suggest you try using Process Explorer from www.sysinternals.com to
> figure out who has the file open. Most of the time it should be able to
> tell you exactly who has locked the file - at least as long as it's done
> from userspace. I'm not 100
> There were several reports of "unable to read/write" on
> Pg8.0.x win32 port:
>
> http://archives.postgresql.org/pgsql-bugs/2005-02/msg00181.php
>
> I encounter this several times and finally I catch the
> GetLastError() number. It is
>
> 32, ERROR_SHARING_VIOLATION
> The process can
