2008/7/13 Alejandro D. Burne <[EMAIL PROTECTED]>:
> 2008/7/13 Pavel Stehule <[EMAIL PROTECTED]>:
>> Hello
>>
>> safe it to pgfoundry http://pgfoundry.org/
>> regards
>> Pavel Stehule
>>
>>
>
> May be to much for including in pgfoundry, I think to build a place to
> share code developed in postgres
2008/7/13 Pavel Stehule <[EMAIL PROTECTED]>:
> Hello
>
> safe it to pgfoundry http://pgfoundry.org/
> regards
> Pavel Stehule
>
>
May be to much for including in pgfoundry, I think to build a place to
share code developed in postgres functions (plpgsql, plpython, etc)
and to categorize them. I can
On Sat, Jul 12, 2008 at 11:14:27PM -0300, Alejandro D. Burne wrote:
> Hi, I need to write a function that gives me a password string, no
> just a numbers-characters string; something like people wrote in php,
> its based on determined syllables and numbers.
> I think it be useful to other people,
Hello
safe it to pgfoundry http://pgfoundry.org/
regards
Pavel Stehule
2008/7/13 Alejandro D. Burne <[EMAIL PROTECTED]>:
> 2008/7/12 Alejandro D. Burne <[EMAIL PROTECTED]>:
>> Hi, I need to write a function that gives me a password string, no
>> just a numbers-characters string; something like p
2008/7/12 Alejandro D. Burne <[EMAIL PROTECTED]>:
> Hi, I need to write a function that gives me a password string, no
> just a numbers-characters string; something like people wrote in php,
> its based on determined syllables and numbers.
> I think it be useful to other people, is there a site whe
Thanks Tom & ludwig, I understand now.
Glyn Astill
- Original Message
From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
To: pgsql-general@postgresql.org
Sent: Friday, 28 March, 2008 3:24:34 PM
Subject: Re: [GENERAL] Users, groups and inheritance questions
Hello Glyn,
Hello Glyn,it's confusing, but You didn't read the manual very carefully! Short excerpt:The INHERIT attribute governs inheritance of grantable privileges (that is, access privileges fordatabase objects and role memberships). It does not apply to the special role attributes set by CREATEROLE and ALT
Glyn Astill <[EMAIL PROTECTED]> writes:
> I thought that if user 'test' was in group 'admins' and I specified INHERIT
> then it'd inherit those permissions?
No, inheritance of permissions only works for GRANT-able permissions;
the special role properties like CREATEDB are outside that scope.
I
On Mon, Jun 20, 2005 at 05:17:57PM -0700, Teunis Peters wrote:
>
> however - I'd like to restrict access to specific records and groups of
> records (based on another table) - and I'm not even sure where to start
> looking. I suspect I actually need to look into triggers and/or
> embedded libr
The system administrator will need to be able to see it, and will need
remote
access to it.
The security requirements are extremely high, the standard in this case
is set
by the state, so encryption will be a must.
I hope you remark that these two are incompatible.
* For instance 'extreme
The system administrator will need to be able to see it, and will need remote
access to it.
The security requirements are extremely high, the standard in this case is set
by the state, so encryption will be a must.
the table itself will need to be accessed by triggers, so the encryption plus
the
On Tue, Jan 18, 2005 at 12:35:01AM -0600, [EMAIL PROTECTED] wrote:
>
> I need a way to link every user name to a unique ID held in a table in the
> database. I've tried several ways of doing this but all of which are not
> secure
> enough. It's essential that no one be able to view the user nam
victor wrote:
> I have to implement a structure of rights.
> I'm intrested if postgresql can restrict these
> operations(insert, update, select, delete) for a specified postgresql
> user.
> If this is possible, please tell me were could I find some
> documentation about this subject.
C G wrote:
Dear All,
I wonder if anyone can advise me with this problem.
1. A user logs into the database (through web, webservice, some other
piece of software) - connect(user="joe",passwd="blogs")
2. We generate a random session key which will expire in 1 hour. Put
this in table (user, SessK
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You've got to have some kind of "middleware". Apache, custom, whatever.
Basically this piece of middleware gets the session key.
Have the middleware (using a common login) retrieve the ser (and password)
drom the database table and authenticate the u
One possible part of a cron script:
su --command="psql -d $PGUSER -c 'vacuum analyze;' > /dev/null" $PGUSER
where 'PGUSER' has been defined as the appropriate user name. Of course,
you'll need a bit more if your database has a different name.
HTH...
-frank
ot;Adam Lang" <[EMAIL PROTECTED]>; "PGSQL General"
<[EMAIL PROTECTED]>
Sent: Tuesday, September 26, 2000 8:21 AM
Subject: Re: [GENERAL] Users
>
> If you want users to access your database remotely. Goto www.phpwizard.net
> or www.phpwizards.net and look for a product
If you want users to access your database remotely. Goto www.phpwizard.net
or www.phpwizards.net and look for a product call "myPostgresql " (I believe)
which iprovides a web based interface for Postgresql
And ithe program is Free, no licence ietc etc.
On Tue, 26 Sep 2000, Adam Lang wrote:
> T
"Adam Lang" <[EMAIL PROTECTED]> writes:
> i.e. Jane works from home and uses a program that access the database
> remotely. Does Jane need to be a user on the database server as well as a
> user in postgresql?
No. Postgres users don't have to be related at all to Unix users on the
server's syst
On Mon, Sep 25, 2000 at 03:45:59PM -0400, Adam Lang wrote:
> To be a user to interact with postgres, do you have to be a user on the
> system it is installed at?
No (although it's possible to set it up that way if you choose).
Database users are independent of system users.
> i.e. Jane works fro
Read this tutorial it has got everyting you need to know about psql.
Document herewith attached
On Sat, 23 Sep 2000, Chris wrote:
> Greetings,
>
> When ever a normal user (anyaccount besides "postgres") tries to
> run psql they get the following message:
>
> Connection to database 'dank'
On Fri, Sep 22, 2000 at 10:36:53PM +, Chris wrote:
> Greetings,
>
> When ever a normal user (anyaccount besides "postgres") tries to
> run psql they get the following message:
>
> Connection to database 'dank' failed.
> FATAL 1: SetUserId: user "chrisp" is not in "pg_shadow"
You prob
>> The contents of the pg_shadow table are written through to a file on disk
>> called pg_pwd, so all the backends can easily access it. However, this
>> write through is not automatic. The create user and alter user commands
>> take care of that, but if you update pg_shadow directly, your changes
On Thu, 4 Nov 1999 [EMAIL PROTECTED] wrote:
> > CREATE USER sql command updates the file, but an UPDATE on pg_shadow
> > does not.
>
> IMHO, that's a bug:
> It's not forbidden to update or insert into pg_shadow by rule, but if
> I do that I will get inconsistent authentication data.
> Why not re
24 matches
Mail list logo
