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

From Oliver Elphick
Subject [Fwd: Re: [Fwd: Bug#149056: postgresql: should not try in a busy loop when allocating resources]]
Date
Msg-id 1023591204.31149.11954.camel@linda
Whole thread Raw
List pgsql-hackers
Russell, can you provide a test case, or at least explain the
circumstances, please.  Please maintain the Cc list.

-----Forwarded Message-----

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Oliver Elphick <olly@lfix.co.uk>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] [Fwd: Bug#149056: postgresql: should not try in a busy loop when allocating resources]
Date: 08 Jun 2002 22:03:33 -0400

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

--
Oliver Elphick                                Oliver.Elphick@lfix.co.uk
Isle of Wight                              http://www.lfix.co.uk/oliver
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839  932A 614D 4C34 3E1D 0C1C
    "Verily, verily, I say unto you, He that heareth my     word, and believeth on him that sent me, hath
everlastinglife, and shall not come into     condemnation; but is passed from death unto life."
        John 5:24 

pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: revised sample SRF C function; proposed SRF API
Next
From: "Marc G. Fournier"
Date:
Subject: Re: Per tuple overhead, cmin, cmax, OID