"Kevin Grittner" wrote:
> When I was investigating this report:
>
> http://archives.postgresql.org/pgsql-bugs/2011-03/msg00349.php
>
> besides providing a straightforward fix here:
>
> http://archives.postgresql.org/pgsql-bugs/2011-03/msg00352.php
>
> I noted that there was nearby code whi
When I was investigating this report:
http://archives.postgresql.org/pgsql-bugs/2011-03/msg00349.php
besides providing a straightforward fix here:
http://archives.postgresql.org/pgsql-bugs/2011-03/msg00352.php
I noted that there was nearby code which needed review, as it didn't
seem safe wh
