| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Daniel Farina <drfarina(at)acm(dot)org> |
| Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Hannu Krosing <hannu(at)krosing(dot)net>, Daniel Farina <dfarina(at)truviso(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION |
| Date: | 2009-12-30 05:58:55 |
| Message-ID: | 603c8f070912292158p72740e57x62ea70df3470d74b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 30, 2009 at 12:56 AM, Daniel Farina <drfarina(at)acm(dot)org> wrote:
> On Tue, Dec 29, 2009 at 9:46 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> Sure. If you think you can make it work using bytea, that seems
>> clearly better than using an internal type, all things being equal.
>
> I think both are perfectly viable and can be supported simultaneously,
> actually...I simply like INTERNAL because the mechanism and passed
> data structure for when you *do* want to write a C function is just
> really crisp and simple, and is not going to be a source of overhead.
OK. I think we'll have to see the proposed patch before we can really
make a final judgement on this, but hopefully I've at least given you
enough feedback/food for thought to move this forward in a meaningful
way...
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2009-12-30 06:00:25 | Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION |
| Previous Message | Daniel Farina | 2009-12-30 05:56:04 | Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION |