This isn't going to be applied because pg_dump is not broken ... at
least not against CVS tip. You apparently are running a pre-beta
backend that numbered ACL entries from zero.
Got it: The code are up-to-date, but I didn't initdb,
so the system catalog didn't update thus the pg_dump broken.
t
> > [ fix broken CHECK_FOR_INTERRUPTS macro ]
>
> Applied. I see how this might change detection of
> statement_timeout, but I do not actually see what it's got to
> do with deadlock detection.
> In the deadlock situation the process that needs to wake up
> is going to be blocked on a semaphor
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>> How does this fix that case?
> It doesn't. This is why the second version of the patch was required,
> per http://archives.postgresql.org/pgsql-patches/2004-09/msg00039.php.
Okay, I've applied the right version of the patch now ;-)
