Re: Problem with accesing Oracle from plperlu functionwhen using remote pg client. - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Problem with accesing Oracle from plperlu functionwhen using remote pg client.
Date
Msg-id 200903170223.n2H2NqB27335@momjian.us
Whole thread Raw
In response to Re: Problem with accesing Oracle from plperlu functionwhen using remote pg client.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Problem with accesing Oracle from plperlu functionwhen using remote pg client.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > I think any serious tools are now using pg_stat_activity.  I saw we make
> > the change in 8.4 and just document it.  I wouldn't make the change for
> > Oracle but rather for clarity.
> 
> I think this is a non-solution, because it fails to guarantee that the
> process title contains nothing that will confuse Oracle.  As somebody
> already pointed out, it's possible to have parens in a user or database
> name ... and for that matter, how sure are we that parens are the only
> trouble case?  You'll be potentially breaking scripts that work now,
> in order to reduce but not eliminate the problem with Oracle.
> 
> IMHO the right fix is the one that was touched on upthread: have
> DBI-Link temporarily install a plain-vanilla, punctuation-free process
> title (eg, just "postgres") while starting an Oracle connection.

I was suggesting the colon rather to be clearer, not as an Oracle
fix.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: small but useful patches for text searcht
Next
From: Tom Lane
Date:
Subject: Re: Problem with accesing Oracle from plperlu functionwhen using remote pg client.