Re: [COMMITTERS] pgsql/contrib/pg_dumplo (README.pg_dumplo lo_export.c lo_import.c main.c pg_dumplo.h utils.c) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [COMMITTERS] pgsql/contrib/pg_dumplo (README.pg_dumplo lo_export.c lo_import.c main.c pg_dumplo.h utils.c)
Date
Msg-id 10004.974855658@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql/contrib/pg_dumplo (README.pg_dumplo lo_export.c lo_import.c main.c pg_dumplo.h utils.c)  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> tgl@postgresql.org writes:
>> Modified Files:
>> README.pg_dumplo lo_export.c lo_import.c main.c pg_dumplo.h 
>> utils.c 
>>
>> Code review: minor cleanups, make the world safe for unsigned OIDs.
>> Improve documentation, too.

> Doesn't pg_dump handle large objects these days?

It does, so pg_dumplo is probably dead code --- for people running 7.1
or later.  The reason I'm taking an interest in it is that Great Bridge
wants to make it available to people running 6.5.* or 7.0.*, so that
they can get their large objects into newer versions in the first place.

Also, it's possible that someone using pg_dumplo would not want to
change (though I'm not sure why not).  So we probably oughta leave it
in the distro for a version or three anyway.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [COMMITTERS] pgsql/contrib/pg_dumplo (README.pg_dumplo lo_export.c lo_import.c main.c pg_dumplo.h utils.c)
Next
From: "Christopher Kings-Lynne"
Date:
Subject: RE: Crash during WAL recovery?