Re: unresolved bugs - Mailing list pgsql-hackers

From Tom Lane
Subject Re: unresolved bugs
Date
Msg-id 25892.1262810199@sss.pgh.pa.us
Whole thread Raw
In response to unresolved bugs  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: unresolved bugs
Re: unresolved bugs
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> The first of these in particular is a fairly detailed report of what
> looks might be a fairly serious problem.

> pg_listener entries deleted under heavy NOTIFY load only on Windows
> http://archives.postgresql.org/pgsql-bugs/2009-12/msg00274.php

Yeah, that needs to be looked at by a Windows expert (ie not me).

> COPY staments with paths containing non-ASCII characters under WinXP
> http://archives.postgresql.org/pgsql-bugs/2009-12/msg00267.php

The general question of what to do with non-ASCII paths is still open.
I don't think there's any consensus about what to do about it, mainly
because it's not clear that we know what encoding is in use in the
filesystem.  In any case, defining the problem as limited to COPY,
or to Windows, seems to me to be missing the point.

> BUG #5245: Full Server Certificate Chain Not Sent to client
> http://archives.postgresql.org/pgsql-bugs/2009-12/msg00145.php

Not clear to me whether this is a bug, or at least our bug.
Isn't that behavior entirely openssl's to determine?

> BUG #5236: Aparent bug in ecpg
> http://archives.postgresql.org/pgsql-bugs/2009-12/msg00078.php

Michael needs to look at that one.

> incorrect exit code from psql with single transaction + violation of
> deferred FK constraint
> http://archives.postgresql.org/pgsql-bugs/2009-10/msg00039.php

Seems like a bug to me too, or at least dubious.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Stefan Kaltenbrunner
Date:
Subject: Re: snapshot generation broken again...
Next
From: Tom Lane
Date:
Subject: Re: snapshot generation broken again...