From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Hannu Krosing <hannu(at)tm(dot)ee>, Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Chris <chris(at)bitmead(dot)com>, Postgres Hackers List <hackers(at)postgresql(dot)org> |
Subject: | Re: OO Patch |
Date: | 2000-05-19 23:19:38 |
Message-ID: | 200005192319.TAA23678@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
> Hannu Krosing <hannu(at)tm(dot)ee> writes:
> >> Certainly libpq is unprepared to support
> >> multiple tuple types returned in one SELECT
>
> > IIRC Bruce removed that feature in Pg95 days claiming that it would
> > not be needed. If backend starts to support it again it would be
> > relatively easy to put back in.
>
> Would it? libpq's internals might not care much, but it seems to me
> that a rather significant API change would be needed, thus risking
> breaking client applications. I'd want to see how the libpq API
> changes before deciding how easy or hard this is ...
Since this came up, I don't remember removing any of this. I may have
given the OK to do it, though.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-05-19 23:21:47 | Re: Performance (was: The New Slashdot Setup (includes MySql server)) |
Previous Message | Tom Lane | 2000-05-19 22:47:23 | Re: OO Patch |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-05-19 23:21:47 | Re: Performance (was: The New Slashdot Setup (includes MySql server)) |
Previous Message | Tom Lane | 2000-05-19 23:16:40 | Sigh: 7.0 pg_dump fails if user table has index on OID |