From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Marko Kreen <markokr(at)gmail(dot)com>, Postgres Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [patch] fix dblink security hole |
Date: | 2008-09-22 02:26:26 |
Message-ID: | 48D70252.4050108@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Yeah. We could make one further refinement: callers that don't care
> about acquiring an error string can pass NULL for the errmsg parameter.
> That tells PQconninfoParse to throw away the errmsg string anyway.
> With that, the minimal case isn't much uglier than your original:
> just need a NULL arg tacked onto the call.
True
> BTW, the usual method for doing this is just to give the caller back the
> errorBuf.data, not incur an additional strdup that could fail.
OK, was entirely sure that was safe.
New patch attached.
Joe
Attachment | Content-Type | Size |
---|---|---|
libpq_and_dblink.2008.09.21.2.diff | text/x-patch | 6.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2008-09-22 02:41:29 | Re: Proposal: move column defaults into pg_attribute along with attacl |
Previous Message | Tom Lane | 2008-09-22 02:14:51 | Re: Proposal: move column defaults into pg_attribute along with attacl |