The following bug has been logged online:
Bug reference: 4629
Logged by: Martin Blazek
Email address: mbla...@8bc.com
PostgreSQL version: 8.3.5
Operating system: Windows XP
Description:PL/pgSQL issue
Details:
I try to create the following rule. It doesn't make much
Tom Lane wrote:
Heikki Linnakangas writes:
Dave Page wrote:
It's possible to set a per-database connection limit of < -1, which seems bogus:
Yeah. That's simple to fix, but I'm having trouble wordsmithing the
error message. This is what I came up with:
Why does it need to be anything exce
"Marshall, Steve" writes:
> The solution that seems to work is to call CallNamedPipe repeatedly in a
> loop if it fails.
Seems a bit nervous-making, since there's no principled way to know how
many retries to try.
> I also notice that signals that should fail, do fail. For example,
> signal 3
Tom Lane wrote:
So my opinion is that the real issue here is why is the kill()
implementation failing when it should not. We need to fix that,
not put band-aids in async.c.
I think Tom makes a valid point. To that end, I think the Window's kill
implementation needs to be changed to have th
