From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [COMMITTERS] pgsql/contrib/pg_dumplo (README.pg_dumplo lo_export.c lo_import.c main.c pg_dumplo.h utils.c) |
Date: | 2000-11-22 01:14:18 |
Message-ID: | 10004.974855658@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> tgl(at)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-11-22 01:37:51 | Re: Re: UUNET socket-file-location patch |
Previous Message | Peter Eisentraut | 2000-11-22 01:09:53 | Re: [COMMITTERS] pgsql/contrib/pg_dumplo (README.pg_dumplo lo_export.c lo_import.c main.c pg_dumplo.h utils.c) |
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2000-11-22 01:14:23 | RE: Crash during WAL recovery? |
Previous Message | Peter Eisentraut | 2000-11-22 01:09:53 | Re: [COMMITTERS] pgsql/contrib/pg_dumplo (README.pg_dumplo lo_export.c lo_import.c main.c pg_dumplo.h utils.c) |