Re: [ADMIN] Problem: PostgreSQL 6.5.1 backend crashing.

1999-08-04 Thread Anto Prijosoesilo
Hi again, Here are the most recent cores: This one is from the postgres root directory. I'm not sure what the circumstances behind the crash, but I was trying to kill the postmaster with 'kill pid' because the database became unresponsive at around the time the core was created. Core was genera

Re: [ADMIN] How to set up users etc for Web access?

1999-08-04 Thread Dmitry Morozovsky
On Tue, 3 Aug 1999, Lamar Owen wrote: LO> 3.) You may or may not want the HTTPD_RUN_USER to actually own the LO> tables in question -- however, you will have to GRANT the perms desired. AS I mentioned previously, there's currently no way to prevent user httpd (or whoever under which httpd is run

[ADMIN] unable to dump database with triggers...

1999-08-04 Thread Ronan Fauglas
Hi, I'm currently using postgresql6.5.1 on a Linux RedHat 5.2. I've got some triggers to keep implement foreign keys written in TCL. When I want to dump my database, I get the following error: -- [postgres@blur sql]$ pg_dump -v euro -- last builtin oid is 17120 -- reading user-d

Re: Re: [ADMIN] How to set up users etc for Web access?

1999-08-04 Thread Mark Linvill
On Tue, 3 Aug 1999, pgsql-admin-digest wrote: > >Date: Tue, 03 Aug 1999 19:08:43 -0400 >From: Lamar Owen <[EMAIL PROTECTED]> >Subject: Re: [ADMIN] How to set up users etc for Web access? > >> Gary Robertson wrote: >[snip] > >> We are setting up a Web site using pgsql. I am unsure of which users I

[ADMIN] Cache lookup failed with FUNCTION + TRIGGER

1999-08-04 Thread Stéphane FILLON
I have one table client : create table client( nocli int4, ); create function client() returns opaque as ' begin if new.nocli ISNULL then raise exception "nocli null"; end if; end; ' language 'plpgsql'; create trigger client before insert on client for each row execute procedur

Re: [ADMIN] How to set up users etc for Web access?

1999-08-04 Thread Lamar Owen
Dmitry Morozovsky wrote: > Well, I suppose web site files should NOT be owned by httpd user, but only > readable (and, if needed, executable bu it) via group -- so permissions > should be 640 or 750, respectievly. This prevents possibility to change > web-content from erroneous cgi script, for exa

Re: [ADMIN] How to set up users etc for Web access?

1999-08-04 Thread Lamar Owen
Mark Linvill wrote: > >While I use AOLserver and not apache+php3, the concepts are similar: > > > >1.)The httpd run user (which should not be root, but some unprivileged > >account, such as 'webserver' (in my case, it's actually 'aolserver')) > >should own all html and php files necessary, wi

[ADMIN] JDBC

1999-08-04 Thread Colin
Any ideas on jdbc for postgres and where I can get the software? -Colin Bodor 3GE Development

[ADMIN] libpq.so.2.0 cannot open shared object file

1999-08-04 Thread Camille Begnis
Hello all, I'm new with postgresql and tried to install it on a RedHat 5.2. All works perfectly following instructions up to launching initdb: pg_id: error in loading shared libraries libpq.so.2.0: cannot open shared object file: No such file or directory Even though "ldconfig -v" gives: /usr/

[ADMIN] how to add entry in pg_hba.conf?

1999-08-04 Thread Xing Banghe
Hello, Q: how to add entry in pg_hba.conf? I manually added an entry in pg_hba.conf as: host template1 postgres_IP 255.255.255.0 banghe banghe But as I run the code and got msg: the file pg_hba.conf is crashed. I wonder if I can manually edit this file. (to locally connect postmaster seems n

Re: [ADMIN] Problem: PostgreSQL 6.5.1 backend crashing.

1999-08-04 Thread Anto Prijosoesilo
Following up on the problem, here's a psql session that crashed: access=> begin; BEGIN access=> SELECT Seq, NAS, SessionID, COUNT(*), MIN(ID) AS ID access-> INTO TEMP T1 access-> FROM Session access-> WHERE Account = '72638' access-> GROUP BY Seq, NAS, SessionID; SELECT ac

Re: [ADMIN] Problem: PostgreSQL 6.5.1 backend crashing.

1999-08-04 Thread Bruce Momjian
Please send a reproducable sample, with CREATE TABLE, INSERT, etc. > Following up on the problem, here's a psql session that crashed: > > access=> begin; > BEGIN > access=> SELECT Seq, NAS, SessionID, COUNT(*), MIN(ID) AS ID > access-> INTO TEMP T1 > access-> FROM Session > access->

Re: [ADMIN] Problem: PostgreSQL 6.5.1 backend crashing.

1999-08-04 Thread Anto Prijosoesilo
On Wed, 4 Aug 1999, Bruce Momjian wrote: > Please send a reproducable sample, with CREATE TABLE, INSERT, etc. My table is rather large so here's one small sample. This one doesn't crash, but it hangs on DELETE using up 100% CPU. This one is tested on FreeBSD 3.2-STABLE. CREATE TABLE Test ( A

Re: [ADMIN] Problem: PostgreSQL 6.5.1 backend crashing.

1999-08-04 Thread Bruce Momjian
> On Wed, 4 Aug 1999, Bruce Momjian wrote: > > > Please send a reproducable sample, with CREATE TABLE, INSERT, etc. > > My table is rather large so here's one small sample. This one doesn't > crash, but it hangs on DELETE using up 100% CPU. This one is tested on > FreeBSD 3.2-STABLE. > > CREATE

Re: [ADMIN] Problem: PostgreSQL 6.5.1 backend crashing.

1999-08-04 Thread Bruce Momjian
> On Wed, 4 Aug 1999, Bruce Momjian wrote: > > > Please send a reproducable sample, with CREATE TABLE, INSERT, etc. > > My table is rather large so here's one small sample. This one doesn't > crash, but it hangs on DELETE using up 100% CPU. This one is tested on > FreeBSD 3.2-STABLE. > > CREATE

Re: [ADMIN] Problem: PostgreSQL 6.5.1 backend crashing.

1999-08-04 Thread Anto Prijosoesilo
On Thu, 5 Aug 1999, Bruce Momjian wrote: [...] > Here is a backtrace with gdb: > > --- > > backend> DELETE FROM T1 WHERE Count = 1; > blank > 1: ctid(typeid = 27, len = 6, typmod = -1, byval = f) >