Hello!
As a reply to my question I got the following answers:
1. do you have the file 'plpgsql.so' in /usr/local/pgsql/lib ?
The answer is yes!
Otherwise I would receive
"ERROR: stat failed on file '/usr/local/pgsql/lib/plpgsql.so': No such file
or directory"
2. Just for this test, chang
> Good to know, but limited. to get the historical info, you'd have to continually
>spawn
> ps and either generate a lot of overhead or miss events.
>
> I think Stephen and I have roughly similar desires (ref "Logging Access" Sun, 03 Oct
>1999 23:09:06 -0400)
> It's not too hard to get the back
>> Hello,
>>
>> I was wondering if there was a way in postgres to monitor
>> database sessions.
>>
>> I'd like to be able to get a list of currently open sessions
>> with information like user id, connection time etc.
>>
>> Also I'd like to be able to see a history of sessions; again
>> user
Here is my suggestion:
Just for this test, change plpgsql.so access code as 777,
after you test, change it back as 640.
Macht das schoen?
Grusse,
--Bangh
Reiner Dassing wrote:
> Hello!
> After installation the PostgreSQL Version 6.5.2 on Digital Unix V4.0F
> I did the regression tests.
>
> T
On Mon, 11 Oct 1999, Reiner Dassing wrote:
> Hello!
> After installation the PostgreSQL Version 6.5.2 on Digital Unix V4.0F
> I did the regression tests.
>
> The test "plpgsql" is that one for which I do not have a solution.
>
> The file "src/test/regress/result/plpgsql.out" shows:
>
> QU
Hello!
After installation the PostgreSQL Version 6.5.2 on Digital Unix V4.0F
I did the regression tests.
The test "plpgsql" is that one for which I do not have a solution.
The file "src/test/regress/result/plpgsql.out" shows:
QUERY: insert into WSlot values ('WS.001.1a', '001', '', '');
ER
