About the last point, my answer is "yes". Yes I see a reason why one could be able to
limit overall database access to one/all users : this could allow maintenance on the
DB without turning the whole installation off. All users are temporarilly revoked all
access.
One could think about many oth
Wow! I didn't expect such good-natured responses! Almost immediately
after my first post, I remembered the whole GRANT issue and posted a
retraction--which I guess was unnecessary. (I expected a storm of
RTFMs, etc. after realizing my oversight.)
I appreciate the responses though, and they spu
Hi,
You just need to grant previlige SELECT to the user nobody on those tables.
check SQL command grant.
--
Bangh
Mike Edwards wrote:
> Hello all,
> My apologies if this has been covered here, but the archives are choking
> and TFMs don't seem to cover this too deeply.
> I am using PostgreSQL
It sounds like you need to check out how to GRANT permissions.
while in the db:
GRANT SELECT ON TO NOBODY
That's off of the top of my head, but should provide enough to point you in
the right direction.
At 09:45 AM 3/16/2000 -0600, Mike Edwards wrote:
>Hello all,
>My apologies if this has b
On Thu, 16 Mar 2000, Karel Zak - Zakkr <[EMAIL PROTECTED]> wrote:
> On Thu, 16 Mar 2000, KOOPMAN,JON (A-SantaClara,ex1) wrote:
> > Thanks for the quick response,
> >
> > o Possibly add a permission structure to database level ACL
> >that can turn off read privilege to a database to certain
>
Check out the GRANT command in postgres; you'll want to do something like:
CREATE USER nobody WITH PASSWORD ;
GRANT SELECT ON , TO nobody;
However, I like to use suExec under apache to have things run by a
different user; that offers somewhat more security. I have scripts that
need, for exampl
On Thu, 16 Mar 2000, KOOPMAN,JON (A-SantaClara,ex1) wrote:
> Thanks for the quick response,
>
> o Possibly add a permission structure to database level ACL
>that can turn off read privilege to a database to certain
>/all users. Is there any reason to limit database
>connectivity d
Please disregard my previous post as there was no reason for me to be
hasty. I believe I have found the problem--it lies between my ears.
Also, please refrain from flaming me as I will be too busy flogging
myself with thorn bushes to reply.
Humbly,
Mike
--
Mike Edwards, MIS
Edwards Graphic Ar
in postgresql 6.4.2, we have tried a pgdump and pgdumpall and then restore.
something in the script file bombs every time. i would like to move the
data and index files from 6.4.2 to 6.5.3. could i re-create the database
manually in 6.5.3, manually create the tables and indexes, and then
ph
Hello all,
My apologies if this has been covered here, but the archives are choking
and TFMs don't seem to cover this too deeply.
I am using PostgreSQL with PHP/Apache. PHP connects to Postgres as
Linux user "nobody" (the user running the Apache daemon) unless a
username and password is explicitl
Thanks for the quick response,
My thoughts on this are:
o SQL command "create database" should take argument for
DBA username. Currently you must do a create database,
and then if you want it owned by someone else, update
the "pg_database" class manually with a 'sysid' for
the new
On Wed, 15 Mar 2000, KOOPMAN,JON (A-SantaClara,ex1) wrote:
> In the documentation page:
>
> http://www.posgresql.org/doxlist.html - Chapter 8. Security in
> the first section I see:
>
> "Each user in Postgres is assigned a username, and (optionally) a
> password. By default, users do not have
Florian Baumert tchatche...
>
> I think it's related to corrupt database or index files, but was never
> able to
> confirm this.
>
from my experience, sometimes, you have a "stress query"
who need a lot of memory, and postgres create huge files
named pg_sorttemp* in the
Mattias Norlander wrote:
>
> Hi!
>
> I've been running postgres for an online sports service for some
> months now. Everything has worked quite smoothly, but this morning
> something strange happend.
>
> Two postgres processess started by the webserver each reached over
> 300M in size and slowe
Hi!
I've been running postgres for an online sports service for some
months now. Everything has worked quite smoothly, but this morning
something strange happend.
Two postgres processess started by the webserver each reached over
300M in size and slowed the machine down to a crawl. They had bee
15 matches
Mail list logo
