>
> Yes, is that your pg_hba.conf line? 'password' is insecure over
> networks you don't trust.
Yes, we're using 'password password' in our pg_hba.conf file. I trust my
network (so far).
-ron
---(end of broadcast)---
TIP 1: subscribe and unsub
> OK, how do secondary passwords work in pg_hba.conf. It requires
> clear-text 'password', right, because the password is already crypt-ed
> in the file.
I presume that you're referring to passwords being transmitted clear text?
> One idea I had was to look for a colon in the username, and if
> As for 7.3, maybe we can get that done in time of everyone
> likes it. If
> we can't, what do we do? Do we re-add the secondary password
> file stuff
> that most people don't like? My big question is how many other
> PostgreSQL users figured out they could use the secondary
> password fil
> > Schema handling - ready? interfaces? client apps?
>
> The backend will be ready (it's not quite yet). pg_dump is ready.
> psql is very definitely not ready, nor is pgaccess. I don't know the
> status for JDBC or ODBC; any comments? The other interface libraries
> probably don't care.
>
>
> As part of createdb, the new database will have to have it's public
> schema changed to world-writable.
I have to admit that much of the schema related discussion has been over my
head, but I think what I understand you to be saying here is that the
default would be to allow anybody to create t
Argh. I just realized that I gave this the wrong subject-- it should've been
"Can't pg_restore large objects"
> Digging a bit, I've discovered this:
> 1) usesysid 1 owns the database in the old server, but all
> the tables are
> owned by 'qvowner' (and others).
> 2) qvowner does not have dba pr
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 31, 2002 3:24 PM
> To: Ron Snyder
> Cc: pgsql-hackers
> Subject: Re: [HACKERS] Can't import large objects in most
> recent cvs (20020531 -- approx 1pm PDT)
>
>
I'm trying to determine if database growth (with LO) that I'm seeing during
a pg_restore is fixed by the patch identified at
http://archives.postgresql.org/pgsql-hackers/2002-04/msg00496.php , but when
I attempt to restore from a 7.2.1 created dump into my newly created
7.3devel database, I get th
> >
> > But I recall a number of rounds of bug-fixes concerning quoting in
> > the pgsql shell scripts, so I'd not be surprised in the
> least to hear
> > that pre-7.2 PG releases get this wrong. Or for that
> matter, we might
> > still have some problems in this line on some platforms with od
as a timestamp.))
-ron "who's off to sub to pgsql-odbc now"
> -Original Message-
> From: Hiroshi Inoue [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, May 04, 2002 7:09 AM
> To: Tom Lane
> Cc: Ron Snyder; [EMAIL PROTECTED]; pgsql-hackers
> Subject: RE:
10 matches
Mail list logo
