[Fwd: Re: [Fwd: Bug#149056: postgresql: should not try in a busy loop when allocating resources]]

From: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>
To: russell(at)coker(dot)com(dot)au
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: [Fwd: Re: [Fwd: Bug#149056: postgresql: should not try in a busy loop when allocating resources]]
Date: 2002-06-09 02:53:24
Message-ID: 1023591204.31149.11954.camel@linda
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sss(dot)pgh(dot)pa(dot)us>
To: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>
Cc: pgsql-hackers(at)postgresql(dot)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(at)lfix(dot)co(dot)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(dot)Elphick(at)lfix(dot)co(dot)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
everlasting life, and shall not come into
condemnation; but is passed from death unto life."
John 5:24

Browse pgsql-hackers by date

  From Date Subject
Next Message Marc G. Fournier 2002-06-09 05:17:10 Re: Per tuple overhead, cmin, cmax, OID
Previous Message Joe Conway 2002-06-09 02:32:04 Re: revised sample SRF C function; proposed SRF API