Re: [Fwd: Bug#149056: postgresql: should not try in a busy loop when allocating resources] - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [Fwd: Bug#149056: postgresql: should not try in a busy loop when allocating resources]
Date
Msg-id 2408.1023588213@sss.pgh.pa.us
Whole thread Raw
In response to [Fwd: Bug#149056: postgresql: should not try in a busy loop when allocating resources]  (Oliver Elphick <olly@lfix.co.uk>)
Responses Re: [Fwd: Bug#149056: postgresql: should not try in a busy  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Oliver Elphick <olly@lfix.co.uk> forwards:
> When trying to create a semaphore Postgresql 7.2.1-3 will try 400,000 times=
>  per
> second if it has problems.

AFAICS it will try *once* and abort if it fails.  Can you provide a
reproducible test case for the above behavior?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Default privileges for new databases (was Re: Can't import large objects in most recent cvs)
Next
From: Bruce Momjian
Date:
Subject: Re: Project scheduling issues (was Re: Per tuple overhead,