See the psql documentation:
http://www.postgresql.org/docs/8.0/interactive/app-psql.html
-W
--password
Cause psql to prompt for a password before connecting to a database. This
will remain set for the entire session, even if you change the database
connection with the meta-command \connect.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane wrote:
> "Milen A. Radev" <[EMAIL PROTECTED]> writes:
>
>>Two queries - 2 seconds apart:
>
>
>>template1=# SELECT datname, age(datfrozenxid) FROM pg_database;
>> datname | age
>>- ---+-
>> xxx1 | 1519763573
>
Tom,
On Mar 11, 2005, at 1:51 AM, Tom Wallick wrote:
prompt request the password AUTOMATICALLY.
How can I clean/flush out the md5 passwords I
originally created and start over alter the two user
accounts 'postgres' and 'tomwallick' to simply have
regular password athentication. Keep in mind
'postgr
Hi Tom,
On Mar 11, 2005, at 8:27 AM, Tom Wallick wrote:
You stated to 'add' the line in this file under
'local'
but there is a line there already as you can see,
which
has values 'local' 'all' 'all' 'trust' set already.
Do I add the line you recommended right after that
line and leave the one befor
On Thu, Mar 10, 2005 at 09:01:21 -0800,
Hemapriya <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Can anybody know how the following statement work.
>
> Grant ALL on SCHEMA test to user 'user1';
>
> will the user be able to have all the privileges on
> all the objects/tables on schema test? Or he can onl
Thanks very much Tom for you input -
The guys at AMCC are suggesting that the firmware on the controller
card crashed, causing the card to basicaly stop IO operations. This
would explain why postgres could not recover and re-read WAL, because
/dev/sdc and sdd were inaccessible at that time.
I th
Hello
I' am new in the forum amd I send the question below to the forum because I
thought that I could get a statement whether I do a mistake or whether it is a
bug. And because I hoped to get a pointer what I can do to solve the problem
;-)
I try to restore a dump of a PostgreSQL 7.4 db int
On Mar 11, 2005, at 10:17 AM, Gregor Schon wrote:
C:\Programme\PostgreSQL\8.0\bin>psql phprvitadb <
C:\Programme\PostgreSQL\8.0\bin\phprvitadb200503082100.dump -U gsc
I think '<' is a problem on Windows. Try
C:\Programme\PostgreSQL\8.0\bin>psql -f
C:\Programme\PostgreSQL\8.0\bin\phprvitadb200503
"Milen A. Radev" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> So you managed to execute about 6000 transactions in those two seconds.
>> Doing what?
> Well that could be the problem - I'm 99.99% positive we do not execute
> so many transactions - may be 30-40 thousand per day and that's only f
On Fri, Mar 11, 2005 at 12:06:16PM +0200, Milen A. Radev wrote:
> Tom Lane wrote:
>
> > So you managed to execute about 6000 transactions in those two seconds.
> > Doing what?
>
> Well that could be the problem - I'm 99.99% positive we do not execute
> so many transactions - may be 30-40 thousand
Tom Lane wrote:
> Bruce Momjian writes:
> > I am now thinking we need to make this "10" a GUC variable for just such
> > cases. This is not the first request for this.
>
> At most it's the second or third request ... and this is hardly the only
> repetitive disk hit in Postgres. I can't get exc
Interesting. That makes sense, though. So, is there a good way to lock
a set of rows using SELECT FOR UPDATE in plpgsql? I assume using
PERFORM would yield the same problem, because it immediately discards
the results.
Thanks!
Kris
Tom Lane wrote:
Kris Kiger <[EMAIL PROTECTED]> writes:
In
Adrian Nida wrote:
> All,
>
> I visited #postgresql @ FreeNode and asked about how to make pg use pam
> about a week ago (specifically I wanted to auth against LDAP). I was
> told to figure it out and write a doc...
>
> Here is my attempt at doing so: http://itc.musc.edu/wiki/PostGreSQL
On Fri, Mar 11, 2005 at 11:42:53AM -0500, Bruce Momjian wrote:
> Adrian Nida wrote:
> > All,
> >
> > I visited #postgresql @ FreeNode and asked about how to make pg use pam
> > about a week ago (specifically I wanted to auth against LDAP). I was
> > told to figure it out and write a doc...
Hello John
Thank you very much - that released the lock and the dump could be
restored. That helped me a lot!
Best regards and a nice weekend
Gregor
John DeSoi <[EMAIL PROTECTED]> schrieb am 11.03.05 16:47:07:
On Mar 11, 2005, at 10:17 AM, Gregor Schon wrote:
C:\Programme\PostgreSQL\8.0\bin>ps
Here is my attempt at doing so: http://itc.musc.edu/wiki/PostGreSQL
I get a "not exists" error on that URL.
Sorry, I renamed the URL after someone pointed out the correct spelling.
This was a link to the old one. I apologize for the confusion, the
right URL is:
http://itc.musc.edu/wiki/Post
Kris Kiger <[EMAIL PROTECTED]> writes:
> Interesting. That makes sense, though. So, is there a good way to lock
> a set of rows using SELECT FOR UPDATE in plpgsql? I assume using
> PERFORM would yield the same problem, because it immediately discards
> the results.
I think PERFORM would work
* Adrian Nida <[EMAIL PROTECTED]> [0307 18:07]:
>
> >>Here is my attempt at doing so: http://itc.musc.edu/wiki/PostGreSQL
>
> >I get a "not exists" error on that URL.
> Sorry, I renamed the URL after someone pointed out the correct spelling.
> This was a link to the old one. I apologize for t
18 matches
Mail list logo
