"Nikolay Mijaylov" <[EMAIL PROTECTED]> writes:
> Thank for responce.
>
> the php is installed as CGI-BIN executable. I think "keep the connections
> open" option is not applicable here. I do this because every user works
> under its own uid and gid, instead all under "nobody".
>
> i dont have a
Michael Ansley <[EMAIL PROTECTED]> writes:
> dev=# create address (addr varchar(50), postcode varchar(9));
> dev=# create client (name varchar(30), addr address);
> dev=# insert into client values ('Michael');
> dev=# insert into address values ('11 Windsor Close', 'RH16 4QR');
> INSERT 18935 1
>
Yes, it sounds like a persistent connection problem with PHP. I know they
help with load speed of postgres, but we have had problems with them.
> -Original Message-
> From: Gunnar R|nning [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, October 05, 2000 8:35 AM
> To: Nikolay Mijaylov
> Cc:
"Nikolay Mijaylov" <[EMAIL PROTECTED]> writes:
> The problem is that PHP is auto killing after a while (1-2 min), but the pos
> tgres backend process stay (and works about 2 or many more hours). Soon all
> Linux is filled with 64 postgres processes, free memory is 0 and Linux, free
> ze :)
>
Th
Title: Object syntax
Given the following table definitions, and data inserts:
dev=# create address (addr varchar(50), postcode varchar(9));
dev=# create client (name varchar(30), addr address);
dev=# insert into client values ('Michael');
dev=# insert into address values ('11 Windsor Close',
--
The reboots are for hardware upgrades!
"http://www.nmmm.nu"; < [EMAIL PROTECTED] >
-Original Message-
From: Nikolay Mijaylov [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 05, 2000 1:28 PM
To: [EMAIL PROTECTED]
Subjec
Tim Uckun wrote:
> At 05:48 PM 10/5/2000 +1100, you wrote:
>
> >I believe this is because the OIDs are not identical. Internally, Postgres is
> >referring to the OIDs and not to the table name. Might be wrong, I am only a
> >postgres newbie, but I think this is the case.
>
> Interesting this makes
At 05:48 PM 10/5/2000 +1100, you wrote:
>I believe this is because the OIDs are not identical. Internally, Postgres is
>referring to the OIDs and not to the table name. Might be wrong, I am only a
>postgres newbie, but I think this is the case.
Interesting this makes sense.
>I don't think it is
Wade D. Oberpriller wrote:
> Hello all,
>
> I was wondering if PostgreSQL protects itself when executing user-defined
> functions? Or does it go under the assumption that all user-defined functions
> will NOT crash (if they do you have a serious problem and need to fix the
> function)?
>
> We are
