Обсуждение: PL/pgSQL

Hello,
I've asked a question, about possibility of PL/pgSQL to work
on OS BSDI-3.1. But I haven't got answer.(Thanx -Jose'-, now I know that it
works
on Linux !).
But is there OS-oriented mailing list, where I can discuss my OS related
problems?

Thank you,
---------------------------
Sergei Chernev
Internet: ser@nsu.ru
Phone: +7-3832-397354

[Charset koi8-r unsupported, filtering to ASCII...]
> Hello,
> I've asked a question, about possibility of PL/pgSQL to work
> on OS BSDI-3.1. But I haven't got answer.(Thanx -Jose'-, now I know that it
> works
> on Linux !).
> But is there OS-oriented mailing list, where I can discuss my OS related
> problems?

In 6.4, it should work on all platforms.  I know it works on bsdi 4.0.

What problems are you seeing.

--
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

> In 6.4, it should work on all platforms.  I know it works on bsdi 4.0.
Hello,
>
> What problems are you seeing.

I still have 3.1 :((

When I install plpgsql language, and prepare one test:
=>CREATE FUNCTION f_test () RETURNS abstime AS '
=>        BEGIN
=>                RETURN \'now\';
=>        END;
=>' LANGUAGE 'plpgsql';
CREATE
EOF
Then I do:
=> select f_test();
It tells me, that:
pqReadData() -- backend closed the channel unexpectedly.
        This probably means the backend terminated abnormally before or
while processing the request.
We have lost the connection to the backend, so further processing is
impossible.
  Terminating.

After that, another programms, which was connected to postgres, loose
connection.
Regression test falls on PL/pgSQL.


With best wishes,
---------------------------
Sergei Chernev
Internet: ser@nsu.ru
Phone: +7-3832-397354

> After that, another programms, which was connected to postgres, loose
> connection.
> Regression test falls on PL/pgSQL.

This is what really has me stumped.  The regression tests fail?  I
wonder if I broke dynamic linking for bsdi 3.1.  Check the regression
tests for other errors, like the LOAD command.

--
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

> > After that, another programms, which was connected to postgres, loose
> > connection.
> > Regression test falls on PL/pgSQL.
>
> This is what really has me stumped.  The regression tests fail?  I
> wonder if I broke dynamic linking for bsdi 3.1.  Check the regression
> tests for other errors, like the LOAD command.
H-m-m, No load :((
Here is my regress.out:

=============== Notes...                              =================
postmaster must already be running for the regression tests to succeed.
The time zone is now set to PST8PDT explicitly by this regression test
 client frontend. Please report any apparent problems to
   ports@postgresql.org
See regress/README for more information.

=============== destroying old regression database... =================
=============== creating new regression database...   =================
=============== running regression queries...         =================
boolean .. ok
char .. ok
name .. ok
varchar .. ok
text .. ok
strings .. ok
int2 .. failed
int4 .. failed
int8 .. ok
oid .. ok
float4 .. ok
float8 .. failed
numerology .. ok
point .. ok
lseg .. ok
box .. ok
path .. ok
polygon .. ok
circle .. ok
geometry .. failed
timespan .. ok
datetime .. ok
reltime .. ok
abstime .. ok
tinterval .. ok
horology .. ok
inet .. ok
comments .. ok
opr_sanity .. ok
create_function_1 .. ok
create_type .. ok
create_table .. ok
create_function_2 .. ok
constraints .. ok
triggers .. ok
copy .. ok
create_misc .. ok
create_aggregate .. ok
create_operator .. ok
create_view .. ok
create_index .. ok
sanity_check .. ok
errors .. ok
select .. ok
select_into .. ok
select_distinct .. ok
select_distinct_on .. ok
select_implicit .. ok
select_having .. ok
subselect .. ok
union .. ok
aggregates .. ok
transactions .. ok
random .. failed
portals .. ok
misc .. ok
arrays .. ok
btree_index .. ok
hash_index .. ok
select_views .. ok
alter_table .. ok
portals_p2 .. ok
rules .. ok
install_plpgsql .. ok
plpgsql .. failed

---------------------------
Sergei Chernev
Internet: ser@nsu.ru
Phone: +7-3832-397354