hi guys,
I'm preparing a new server to host some website postgresql+php4+apache
1.3.x based.
the machine's hardware configuration is:
* amd sempron 3200+ native 64bit
* 1 GB ram DDR2
* chipset nvidia geforce 6100
* controller sata2 silicon image 3112 with RAID functionality
* 2 sata2 hard disk
I can understand the exact error as its not in english :) but it seems like
an authentication problem. Please change 'md5' to 'trust' in pg_hba.conf
file and then use:
pg_ctl -D reload
That will reload the settings for authentication.
Now once the settings are reloaded try reconnecting to the
Title: Signature
Hi Mir,
thanks for your quick answer. We will try this.
For my unterstanding: Why should i use trust instead of md5
? A configuration at another customer (with a domain setting) using
md5 works fine ?
mit freundlichen Grüßen / best regards,
The error you are getting is because of the password not been passed
correctly so 'trust' will let you get in the server without specifying the
correct password, once you are in now you can change the password as you
like using ALTER USER command. Once its done change it back to md5 as it was
befo
I often perform single-table backups using pgadmin.
Recently, a problem occurred while doing that kind of backup using pgadmin
1.6.2 and PostgreSQL 8.2.1 on a Windows server:
When trying to backup a table contained in a specific schema, pg_dump can't
find the table.
For instance, I have a dat
Hi Jim,
Thanks for your reply.
Well..there is no particular reason for knowing the database create
date, but I feel this information is something which should be known,
especially in a development environment where multiple database are
created and deleted. This helps in keep historical information
"=?iso-8859-1?Q?H=E9lder_M._Vieira?=" <[EMAIL PROTECTED]> writes:
> I often perform single-table backups using pgadmin.
> Recently, a problem occurred while doing that kind of backup using pgadmin
> 1.6.2 and PostgreSQL 8.2.1 on a Windows server:
> For instance, I have a database named 'mdg', cont
Hi,
after some test i got that my performance problem described in the
message http://archives.postgresql.org/pgsql-admin/2007-01/msg00116.php
is issued by the linux software raid 1 on my discs (yes the silicon
image controller has only fake raid hardware).
I found this old message that seems the
Hello,
I am currently trying to upgrade PostgreSQL from 8.0 to 8.1 on our development
machine and have run into a problem with RETURN VOID; statements in PL/pgSQL
functions that have a return type of void.
I'm getting errors like the following:
ERROR: RETURN cannot have a parameter in function
>> "Christopher Bland" <[EMAIL PROTECTED]> writes:
>> FATAL: incorrect checksum in control file
>
>Does pg_controldata print anything useful?
>
> regards, tom lane
I *just* re-initialized the database and started over. I didn't think I had a
dump of the original
but then I
"Donald Fraser" <[EMAIL PROTECTED]> writes:
> I'm getting errors like the following:
> ERROR: RETURN cannot have a parameter in function returning void at or =
> near "VOID" at character 2983.
> Does this mean I must edit every function that is declared with RETURNS =
> VOID and remove the RETUR
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Hélder M. Vieira" <[EMAIL PROTECTED]>
Cc:
Sent: Monday, January 15, 2007 3:39 PM
Subject: Re: [ADMIN] Pg_dump behaviour
...
That was the pre-8.2 way to do it; now the right thing would be
-t art.tefh
Sounds like pgadmin
12 matches
Mail list logo
