Re: Dead encoding conversion functions - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Dead encoding conversion functions
Date
Msg-id 6B6F5079-A933-42F8-943D-E9A1EF56B47A@yesql.se
Whole thread Raw
In response to Dead encoding conversion functions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> On 29 May 2019, at 15:03, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Pursuant to today's discussion at PGCon about code coverage, I went
> nosing into some of the particularly under-covered subdirectories
> in our tree,

On a similar, but much less important/interesting note.  I fat-fingered when
compiling isolationtester on the plane over here and happened to compile
src/test/examples, and in there testlo.c and testlo64.c has two dead functions
for which the callsites have been commented out since the Postgres95 import
(and now cause a warning).  Is there any (historic?) reason to keep that code?
It also seems kind of broken as it doesn’t really handle the open() call
failure very well.

cheers ./daniel


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Dead encoding conversion functions
Next
From: Michael Paquier
Date:
Subject: Re: Pinned files at Windows