Re: OIDS (Re: [HACKERS] Well, then you keep your darn columns)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: OIDS (Re: [HACKERS] Well, then you keep your darn columns)
Date: 2000-01-28 05:26:11
Message-ID: 9602.949037171@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>>>> At least the wire protocol supports it and also libpq used to support it,
>>>> until at about time of postgres95/postgreSQL it was removed from libpq as
>>>> "unneeded" (by Bruce IIRC).
>>
>> Bruce, you scoundrel! :-)
>>
>>>> until that time it should have theoretically been possible to
>>>> return tuples of several types and sizes, either by using "select *
>>>> from base* " or unions or functions in backend.

> I have no idea what this was. I could have removed it, but I don't
> remember anything about this.

Actually I might be the guilty party. I recall having seen that libpq
was willing to accept multiple T (tuple descriptor) messages
interspersed in the data returned by a query. But the API that libpq
presents to the application cannot support this, and I concluded after
digging around in the backend that the backend couldn't do it either.
I think I broke libpq's support for it during the rewrite for 6.4.

This is something that might have worked once upon a time, long ago
and far away. But making it work again will take considerably more
than just patching libpq...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-01-28 05:31:26 Re: [SQL] RE: [GENERAL] Problem with SELECT on large negative INT4
Previous Message Chris Bitmead 2000-01-28 05:18:47 ONLY vs "*"