| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Hannu Krosing" <hannu(at)skype(dot)net> |
| Cc: | "David Fetter" <david(at)fetter(dot)org>, "Josh Berkus" <Josh(dot)Berkus(at)Sun(dot)COM>, "Merlin Moncure" <mmoncure(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: real procedures again (8.4) |
| Date: | 2007-10-29 22:18:17 |
| Message-ID: | 87ejfdd0pi.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Hannu Krosing" <hannu(at)skype(dot)net> writes:
> What I was referring to, was a "code cleanup" of libpq several years
> ago, when someone (maybe Bruce IIRC) removed ability to accept multiple
> recordsets from backend altogether, on the basis that it is not used
> anyway.
You can still receive multiple record sets just fine using libpq. psql doesn't
handle them but they're there. When I was doing the concurrent psql patch I
also had it handling multiple record sets.
Something else you may be thinking of, I don't think it's legal to do queries
like "select 1 ; select 2" in the new protocol. That was legal in the old
protocol.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-10-29 22:32:11 | Re: Proposal: real procedures again (8.4) |
| Previous Message | Hannu Krosing | 2007-10-29 21:58:20 | Re: Proposal: real procedures again (8.4) |