On Tue, Mar 17, 2009 at 11:27:54AM +0100, Albe Laurenz wrote:
Tom Lane wrote:
The solution to this is to change the following line in
src/backend/postmaster/postmaster.c:
We're not going to break a bunch of other applications in order to make
some undocumented, unsupported Oracle
On Tuesday 17 March 2009 05:29:48 Tom Lane wrote:
I wrote:
Well, we could certainly debate the change on its own merits, but
I'm not seeing that it's enough nicer to justify a risk of breaking
ps-watching scripts.
Also, on second thought: what about IPv6 addresses? Colon doesn't
look
On Mon, 2009-03-16 at 21:21 +0200, Heikki Linnakangas wrote:
Jonah H. Harris wrote:
On Mon, Mar 16, 2009 at 3:03 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
Someone should raise a support request / whatever they call them with
Oracle to get this fixed on their
On Mon, 2009-03-16 at 14:43 -0400, Jonah H. Harris wrote:
On Mon, Mar 16, 2009 at 2:34 PM, Tom Lane t...@sss.pgh.pa.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
Tom Lane wrote:
The solution to this is to change the following line in
src/backend/postmaster/postmaster.c:
We're not going to break a bunch of other applications in order to make
some undocumented, unsupported Oracle thingie work (until they change
it...). Got another solution?
Yes
On Mon, Mar 16, 2009 at 08:50:36PM -0400, Tom Lane wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Hmm, I wonder if you could do something malicious with it.
There are any number of scenarios where exposing the client command-line
contents to other database users
Thank you for quick answer.
I understand, but when I print from plperlu function notices with result of
`env` they're the same in both cases (from remote and local client).
So it looks like that plperlu function is executing from remote and local
clients with the same set of environment
On Mon, Mar 16, 2009 at 11:09 AM, Tomasz Olszak tols...@o2.pl wrote:
So it looks like that plperlu function is executing from remote and local
clients with the same set of environment variable.
It has nothing to do with the environment variables.
So I don't have a clue how can I iron out
Jonah H. Harris escribió:
On connection, the Oracle client sends the current application name to the
Oracle server (which is listed in the V$SESSION view); in the case of
Postgres, the program name is the current backend process name text.
Because Oracle picks up Postgres' backend text,
Jonah H. Harris wrote:
Finally, my low-level Oracle knowledge does benefit Postgres :)
:-)
It's a TNS parsing error due to a combination of Oracle's use of a
Lispish s-expression-like name-value pair format and Postgres' process
listing format for remote connections.
On connection,
Jonah, you're the man :).
Thank you very much, I tried to solve it for about 2 weeks. I know that few
people in the net have the same problem too.
I simply chanche that line, recompile postgresql and wait for some better
solution.
I know that a lot of people uses DBI-LINK. It simply doesn't
Jonah H. Harris jonah.har...@gmail.com writes:
The solution to this is to change the following line in
src/backend/postmaster/postmaster.c:
We're not going to break a bunch of other applications in order to make
some undocumented, unsupported Oracle thingie work (until they change
it...). Got
On Mon, Mar 16, 2009 at 1:06 PM, Tom Lane t...@sss.pgh.pa.us wrote:
We're not going to break a bunch of other applications in order to make
some undocumented, unsupported Oracle thingie work (until they change
it...). Got another solution?
Unfortunately, that's the way Oracle has done it
On Mon, Mar 16, 2009 at 12:50 PM, Tomasz Olszak tols...@o2.pl wrote:
Thank you very much, I tried to solve it for about 2 weeks. I know that few
people in the net have the same problem too.
No problem :)
--
Jonah H. Harris, Senior DBA
myYearbook.com
On Mon, Mar 16, 2009 at 12:36 PM, Alvaro Herrera alvhe...@commandprompt.com
wrote:
Jonah H. Harris escribió:
Wow, that's a really idiotic thing for Oracle to do.
Well, being able to find out what applications are connected to the database
is nice. But, it would also be nice if they stopped
All,
Probably somebody should resurrect the Oralink project instead.
http://pgfoundry.org/projects/oralink/
--Josh
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Jonah H. Harris escribió:
I first encountered it while working on database links from PG to Oracle at
EnterpriseDB, and the reason Tomasz couldn't find the answer to this online
is because it's such a rare problem that Oracle has no reason to change it.
Really, how many people have
On Mon, Mar 16, 2009 at 2:04 PM, Alvaro Herrera
alvhe...@commandprompt.comwrote:
We already have one; it's called update_process_title.
I have it turned off, and I still see the remote IP/port in the process
list.
--
Jonah H. Harris, Senior DBA
myYearbook.com
Jonah H. Harris wrote:
On Mon, Mar 16, 2009 at 2:04 PM, Alvaro Herrera
alvhe...@commandprompt.comwrote:
We already have one; it's called update_process_title.
I have it turned off, and I still see the remote IP/port in the process
list.
I am thinking the title doesn't update _after_
Bruce Momjian br...@momjian.us writes:
Jonah H. Harris wrote:
I have it turned off, and I still see the remote IP/port in the process
list.
I am thinking the title doesn't update _after_ you turn it off, but it
was updated when the session started.
Yeah, we intentionally set the title
Jonah H. Harris escribió:
On Mon, Mar 16, 2009 at 2:04 PM, Alvaro Herrera
alvhe...@commandprompt.comwrote:
We already have one; it's called update_process_title.
I have it turned off, and I still see the remote IP/port in the process
list.
Yeah, apparently init_ps_display changes the
On Mon, Mar 16, 2009 at 2:26 PM, Jonah H. Harris jonah.har...@gmail.comwrote:
On Mon, Mar 16, 2009 at 2:04 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
We already have one; it's called update_process_title.
I have it turned off, and I still see the remote IP/port in the process
On Mon, Mar 16, 2009 at 2:34 PM, Tom Lane t...@sss.pgh.pa.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,
Alvaro Herrera alvhe...@commandprompt.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
On Mon, Mar 16, 2009 at 02:30:28PM -0400, Jonah H. Harris wrote:
On Mon, Mar 16, 2009 at 2:26 PM, Jonah H. Harris
jonah.har...@gmail.comwrote:
On Mon, Mar 16, 2009 at 2:04 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
We already have one; it's called update_process_title.
Jonah H. Harris wrote:
On Mon, Mar 16, 2009 at 2:34 PM, Tom Lane t...@sss.pgh.pa.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
On Mon, Mar 16, 2009 at 3:03 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
Someone should raise a support request / whatever they call them with
Oracle to get this fixed on their side..
Heh. Why would they fix it when it's only a problem for 1% of their users
in odd
Jonah H. Harris wrote:
On Mon, Mar 16, 2009 at 3:03 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
Someone should raise a support request / whatever they call them with
Oracle to get this fixed on their side..
Heh. Why would they fix it when it's only a problem for 1%
On Mon, Mar 16, 2009 at 3:21 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
Because that's what a respectable business does when a customer runs into a
bug with software they sell.
It's not a bug, it's expected behavior. Not that I think it couldn't be
better handled.
Jonah H. Harris wrote:
On Mon, Mar 16, 2009 at 3:21 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
Because that's what a respectable business does when a customer runs into a
bug with software they sell.
It's not a bug, it's expected behavior.
You really call it
On Mon, Mar 16, 2009 at 5:22 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
Hmm, I wonder if you could do something malicious with it. Like, run a
query along the lines of SELECT $$ (HOST=10.0.0.123) $$, connect()... to
divert the connection to another server.
Not any
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Hmm, I wonder if you could do something malicious with it.
There are any number of scenarios where exposing the client command-line
contents to other database users represents a security hole, quite
independently of whether anything
On Mon, Mar 16, 2009 at 8:50 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Hmm, I wonder if you could do something malicious with it.
There are any number of scenarios where exposing the client command-line
contents to other database
Bruce Momjian br...@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
Tom Lane wrote:
Bruce Momjian br...@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
Jonah H. Harris wrote:
On Mon, Mar 16, 2009 at 8:50 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Hmm, I wonder if you could do something malicious with it.
There are any number of scenarios where exposing the client command-line
Bruce Momjian br...@momjian.us writes:
I was suggesting the colon rather to be clearer, not as an Oracle
fix.
Well, we could certainly debate the change on its own merits, but
I'm not seeing that it's enough nicer to justify a risk of breaking
ps-watching scripts.
I wrote:
Well, we could certainly debate the change on its own merits, but
I'm not seeing that it's enough nicer to justify a risk of breaking
ps-watching scripts.
Also, on second thought: what about IPv6 addresses? Colon doesn't
look like a very good idea at all if you suppose that what's in
38 matches
Mail list logo
