| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Tomasz Olszak <tolszak(at)o2(dot)pl>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Problem with accesing Oracle from plperlu functionwhen using remote pg client. |
| Date: | 2009-03-17 09:34:54 |
| Message-ID: | 1237282494.3953.35.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2009-03-16 at 14:43 -0400, Jonah H. Harris wrote:
> On Mon, Mar 16, 2009 at 2:34 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I'm finding it hard to believe that there is no way to
> override what
> Oracle's client library does --- there are *plenty* of
> situations where
> you don't really want a client command line exposed to the
> whole world.
>
> AFAIK, there is no way to override that. It's very low-level in their
> client stack, is operating-system specific, and has been there
> forever.
But we can easily change what we do, for this specific situation only.
Write a C function to update the process title to something that does
work correctly, then use with update_process_title = off. That way you
can do a specific workaround for this situation without touching the
postmaster code.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2009-03-17 10:27:54 | Re: Problem with accesing Oracle from plperlu functionwhen using remote pg client. |
| Previous Message | Simon Riggs | 2009-03-17 09:32:50 | Re: Problem with accesing Oracle from plperlu functionwhen using remote pg client. |