pgsql: Fix a potential free() of string literal in oid2name, per report - Mailing list pgsql-committers

From neilc@svr1.postgresql.org (Neil Conway)
Subject pgsql: Fix a potential free() of string literal in oid2name, per report
Date
Msg-id 20041202061450.A68FF3A5712@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix a potential free() of string literal in oid2name, per report from
Michael Fuhr. Along the way, fix a bunch of accesses to uninitialized
memory, add a mystrdup() routine and use it to cleanup some code.

Modified Files:
--------------
    pgsql/contrib/oid2name:
        oid2name.c (r1.25 -> r1.26)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/oid2name/oid2name.c.diff?r1=1.25&r2=1.26)

pgsql-committers by date:

Previous
From: momjian@svr1.postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Add: > > * Allow FOR UPDATE queries to do NOWAIT locks >
Next
From: momjian@svr1.postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Rework libpq threaded SIGPIPE handling to avoid interference with