On 2000-01-14, The Hermit Hacker mentioned:
> Side point ... why isn't the apache conf file secure? Only user root
> needs to be able to read it, no?
Huh? You run apache as root?
--
Peter Eisentraut Sernanders väg 10:115
[EMAIL PROTECTED] 75262 Uppsala
http:
On 2000-01-14, Ed Loehr mentioned:
> I'd like to grant read-access to every single DB object in a database
> for one user. I'd hoped for
>
> GRANT SELECT ON * TO
>
> but the '*' syntax is wrong and I don't see an alternative in the
> docs...
>
> How is this done?
The standard doesn't al
On 2000-01-14, Alfred Perlstein mentioned:
> > issue: how to secure cgi's that access postgres
> >
> > problem: passwords for postgres database are stored
> > in plain text in scripts. (lets assume, perl,
> > not a compiled language)
> >
> > points:
> > make cgi dir 711
> >
On 2000-01-14, Rick Delaney mentioned:
> You make some good points, but where is this recommended in the docs? I'd like
> to see more of "serial vs oid" if there is something.
Although I don't represent any official opinion, the tendency among the
developers would seem to be not using oids fo
On 2000-01-15, yura mentioned:
> Hello Adriaan,
>
> Wednesday, January 12, 2000, 4:24:53 PM, you wrote:
>
> AJ> Postgres has a load of text search operators. The most powerful is ~*
> AJ> whcih gives you a case insensitive regular expression search.
>
> AJ> Adriaan
>
> Thank you for reply, bu
On 2000-01-13, Gabriel Fernandez mentioned:
> - What does exactly mean that a mode 'CONFLICTS' with another
> ?
> - Does it mean that another concurrent transactions having
> these modes will have to wait until the first transaction
> have finished (commit or roll b
An array is not quite the same as a result set. What the questioner wanted
(as I understand it) was a function that returned more than one row. That
doesn't work. If you manage to do it via arrays, more power to you.
On 2000-01-13, omid omoomi mentioned:
> Hello,
> Sure you can use arrays as ret
I have Debian 2.1
PostgreSQL 6.5.3
with PHP 3.0.5
e php-pgsql module
I have set up everything. Apache works, php works, pgsql module is
loaded but this is the message whe i try to connect to the db:
Unable to connect to PostgresSQL server: connectDB() failed: Is the
postmaster running and accept
* Peter Eisentraut <[EMAIL PROTECTED]> [000116 09:30] wrote:
> On 2000-01-14, Alfred Perlstein mentioned:
>
> > > issue: how to secure cgi's that access postgres
> > >
> > > problem: passwords for postgres database are stored
> > > in plain text in scripts. (lets assume, perl,
> > >
On Sun, 16 Jan 2000, Il Paolone wrote:
> Unable to connect to PostgresSQL server: connectDB() failed: Is the
> postmaster running and accepting TCP/IP(with -i) connections at
> 'bigpaul' on port '5432'? in /var/www/ciao.php3 on line 34
Is postmaster being started with the '-i' switch??
--
Lamar
Lamar Owen wrote:
>
> On Sun, 16 Jan 2000, Il Paolone wrote:
> > Lamar Owen wrote:
> > > Is postmaster being started with the '-i' switch??
>
I have found with deja, this french problem just now, I am trying, I'll
let you know.
---
You might want to check that you have run initdb. Log in as user postgres
and type:
/usr/local/pgsql/bin/initdb
Then check to make sure that postmaster is actually running, as someone
else suggested.
At 11:21 PM 1/15/00, C.D. Gan wrote:
>I'm just trying to run PGSQL and running the test fo
Peter Eisentraut wrote:
>
> On 2000-01-14, Alfred Perlstein mentioned:
>
> > > issue: how to secure cgi's that access postgres
> > >
> > > problem: passwords for postgres database are stored
> > > in plain text in scripts. (lets assume, perl,
> > > not a compiled language)
> > >
> >
I have updated my port of postgresql on freebsd-current using the
following commands:
# make
# pkg_delete postgresql-6.5.1
# make install
Everything is working well, except for pg_dump which now returns:
pg_dump: couldn't find the template1 database. You are really hosed.
Giving up.
Yet, the tem
* Ron Chmara <[EMAIL PROTECTED]> [000116 16:18] wrote:
> Peter Eisentraut wrote:
> >
> > On 2000-01-14, Alfred Perlstein mentioned:
> >
> > > > issue: how to secure cgi's that access postgres
> > > >
> > > > problem: passwords for postgres database are stored
> > > > in plain text in scrip
Alfred Perlstein wrote:
> * Ron Chmara <[EMAIL PROTECTED]> [000116 16:18] wrote:
Snip_> Of security items.
> All these options don't take into account that perhaps you don't
> want people _on the same box_
Well, I assumed that web clients, using cgi, was the "Subject:",
so I didn't adrdress
16 matches
Mail list logo
