| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jim Vanns <james(dot)vanns(at)framestore(dot)com>, Dmitriy Igrishin <dmitigr(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Bug in libpq implentation and omission in documentation? |
| Date: | 2012-08-13 13:45:13 |
| Message-ID: | 502904E9.5010503@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08.08.2012 17:35, Tom Lane wrote:
> A runtime check for too many parameters seems appropriate. Assuming
> that the error message it throws is well written, I don't think we need
> to adjust the documentation. There are many limitations that are not
> spelled out in the docs, and adding every one of them would not amount
> to a net improvement. Considering that Jim is the first to try this in
> however many years it's been since 7.4, I don't think that everybody
> needs to read about this restriction while they're trying to absorb what
> PQexecParams does.
Runtime check added to the functions that take an nParams argument.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2012-08-13 16:13:17 | sharing variables between client and server again |
| Previous Message | Magnus Hagander | 2012-08-13 10:46:43 | Re: Yet another failure mode in pg_upgrade |