every concurrent cgi script uses its own postgres connection in your
case. you're going to run into more serious problems (e.g. empty pages
for no reason) because of lack of possible postgres connections. so,
1) try mod_perl to speed up your perl scripts
2) think about writing a server which woul
Gary DeSorbo <[EMAIL PROTECTED]> writes:
> I have been having some problems with my database/web server machine
> and ma having difficulty in finding out what the problem is. I have
> two machines configured exactly the same; one for development and one
> for production. Pages on production are
It would seem that SELECT queries are active for reasonably long periods of
time. I would suggest using pgmonitor run as postgres and, using the
"query" functionality, grab the actual SQL being issued and run an EXPLAIN
on it. It is likely that due to either table size, index or statistics
differ
I have been having some problems with my database/web server machine
and ma having difficulty in finding out what the problem is. I have
two machines configured exactly the same; one for development and one
for production. Pages on production are taking up to 10X longer to
load than the same pa
Hello:
Although /etc/init.d/postgresql script is listed in each run level startup
script at /etc/rc#.d, for some reason completely beyond me, postmaster must
be manually started each time I boot up. Any help getting the database
server to automatically start at boot up would be appreciated.
T
Heni Lolov <[EMAIL PROTECTED]> writes:
> ive tried :
> revoke all ON schema public from hal;
> but does not work. Why?
You'd need to revoke the permissions from PUBLIC; they were never granted
specifically to hal, thus the above revoke is a no-op.
Don't forget to revoke CREATE at the database lev
COMPILATION ERROR: Unrecognized header string
This is the message I received when I tried to download 7.3 beta.
Anyone know what it means?
Thanks,
Warren
_
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.
http://join.msn.c
"Mr OCP" <[EMAIL PROTECTED]> writes:
> I am testing the beta 5 version of 7.3, by using make check under solaris 7
> and 8 and it runs just 13 tests as against 77 tests as indicated in the
> README.regression,
I believe this problem is now fixed --- the pg_regress script was
making an unportable
From: Andrew Sullivan <[EMAIL PROTECTED]>
According to my report, yes. I tested 7.3b3 on 2002-10-28.
I'll bet it had to do with a funky path I had, though; probably I
picked up a different awk (there are two on Solaris), because I was
also working on another problem during the same period. (I c
Sorry :)
forgive me please!
ive tried :
revoke all ON schema public from hal;
but does not work. Why?
with drop it worked :)
Ive got :
ERROR: No namespace has been selected to create in
regards,
hal
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> Heni Lolov <[EMAIL PROTECTED]> writes:
> > SO WILL T
Heni Lolov <[EMAIL PROTECTED]> writes:
> SO WILL THERE EVER BE POSSIBLE TO DISALLOW
> OBJECT CREATION TO USERS AND TO GIVE THEM
> ONLY READ ACCESS TO SOME OBJECTS IN A DB?
If you'd quit shouting and RTFM, you'd find out that it's possible in
7.3. (Hint: drop the public schema or revoke privilege
On Tue, Nov 12, 2002 at 10:17:25PM -0500, Bruce Momjian wrote:
> I show the 'awk' added by me on October 19th, actually to get
> postgresql.conf 'autocommit off' working for regression tests:
>
> revision 1.28
> date: 2002/10/19 01:35:43; author: momjian; state: Exp; lines: +1
Hi
I have just downloaded and installed PgSQL 7.3b5.
Unfortunately the same problem is still there. There
is no way to diallow creating tables in the database.
Every user is able to crete tables in every database.
So there is no much sence to disallow users to create
schemas when they can create
13 matches
Mail list logo
