| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(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-16 18:55:30 |
| Message-ID: | 22339.1237229730@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Maybe DBI-Link could set the title to something else before attempting
> the connection. (And perhaps locally set update_process_title to off.)
Making the (unwarranted?) assumption that Oracle's library only captures
the title during connect, it seems like DBI-Link could be made to just
transiently override the title while connecting. There should be no
need to break user-visible behavior for this.
The whole thing seems mighty bizarre though. Given the number of
different ways we have to set the process title, I rather wonder whether
what we do will always determine what Oracle sees, on every platform.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kenneth Marshall | 2009-03-16 18:56:03 | Re: Problem with accesing Oracle from plperlu functionwhen using remote pg client. |
| Previous Message | Jonah H. Harris | 2009-03-16 18:43:16 | Re: Problem with accesing Oracle from plperlu functionwhen using remote pg client. |