From: Thomas G. Lockhart <lockhart@alumni.caltech.edu>
To: David Hartwig <daveh@insightdist.com>
Cc: pgsql-interfaces <pgsql-interfaces@postgresql.org>
Cc: PostgreSQL-development <hackers@postgresql.org>
Cc: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [HACKERS] New pg_type for large object
Date: Fri, 10 Apr 1998 01:18:24 +0000
Message-ID: <352D7360.EB06AADF@alumni.caltech.edu> (raw)
References: <352D51A0.69CE8BB8@insightdist.com>
> What I would like to know is, can a large object data type be added as
> an internal data type? The various "lo_" functions should
> eventually be overloaded (or modified) to be able to use this data
> type. But it is not necessary at this time. I believe this addition
> is a very low risk change, and I would very much like to get to have
> it in the 6.3.2 release for distribution. May I submit the patch, or
> would someone kindly hack it in for us?
I'm not certain exactly what you want (didn't read very closely and it
doesn't fall in an area I've worked with) but it is not likely to be in
v6.3.2 since we're already in the freeze period. However, I would
suggest revisiting the subject just after the release, perhaps roping in
others who have worked with large objects (Peter Mount comes to mind).
There will be a ~2 month period for working on new capabilities, and
this might fit into that.
- Tom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: lockhart@alumni.caltech.edu, daveh@insightdist.com, hackers@postgresql.org, byronn@insightdist.com
Subject: Re: [HACKERS] New pg_type for large object
In-Reply-To: <352D7360.EB06AADF@alumni.caltech.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox