I don't know why postgres is prompting for a password. But you could try
putting the following in your crontab:
su postgres -c 'pg_dump ...'
Simon
2011/3/24 Jaroslav Záruba
> Hello
>
> I have pg_dump command in cron that accesses PostgreSQL under user postgres
> and does not provide a passwor
On Thu, Mar 24, 2011 at 6:49 PM, Willy-Bas Loos wrote:
> BTW, is there a way to find out what particular configure options were used
> for any given (binary) installation?
>
>
The *pg_config* utility prints configuration parameters of the currently
installed version of PostgreSQL
*--configure*
Willy-Bas Loos writes:
> BTW, is there a way to find out what particular configure options were used
> for any given (binary) installation?
Run pg_config.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscri
On Thu, Mar 24, 2011 at 6:09 PM, Stevie wrote:
> Hello pgsql-admins,
>
> we have a problem with our Postgresql 9.0.3 backup database (Ubuntu 10.4).
> The backup and restore is done as described here:
> http://www.postgresql.org/docs/9.0/static/continuous-archiving.html
> If you want to know the
BTW, is there a way to find out what particular configure options were used
for any given (binary) installation?
WBL
On Thu, Mar 24, 2011 at 2:11 PM, Willy-Bas Loos wrote:
> Hi,
>
> I'm not quite sure but it probably means that postgresql was not built with
> kerberos 5 support.
> That would ma
Hi,
I'm not quite sure but it probably means that postgresql was not built with
kerberos 5 support.
That would make sense if you are using a binary install (did not compile
from source), because of the notice at
http://www.postgresql.org/docs/9.0/interactive/auth-methods.html#KERBEROS-AUTH
"Note:
Hello pgsql-admins,
we have a problem with our Postgresql 9.0.3 backup database (Ubuntu
10.4).
The backup and restore is done as described here:
http://www.postgresql.org/docs/9.0/static/continuous-archiving.html
If you want to know the exact steps of backup and restore,please ask.
We restore the
Le 24/03/2011 11:32, Jaroslav Záruba a écrit :
> You nailed it! :)
>
> My regular user has .pgpass, root does not.
> When I remove the --host (and --port) arguments it works like charm. :)
>
> Thanks a lot, Guillaume!
>
You're welcome :)
--
Guillaume
http://www.postgresql.fr
http://dalibo.
On 24 Mar 10:39, Jaroslav Záruba wrote:
> The command line is still the same, when executed under one user it does not
> ask for password, when executed under another (root that is) it does:
> pg_dump --ignore-version --host=localhost --port=5432 --username=postgres
> --file="$BACKUP_FILE" --format
Le 24/03/2011 10:39, Jaroslav Záruba a écrit :
> The command line is still the same, when executed under one user it does not
> ask for password, when executed under another (root that is) it does:
> pg_dump --ignore-version --host=localhost --port=5432 --username=postgres
> --file="$BACKUP_FILE" -
On Tue, Mar 22, 2011 at 1:08 AM, Paul Gross wrote:
> We are using pg_standby to consume WAL files from another postgres
> server. Both servers are running 8.4 on ubuntu lucid. One of the WAL
> files had incorrect permissions:
>
> running restore :cp: cannot open `/some/path/
> 0001
This is what pops up in postgres log whenever I run the command under root,
just when I get prompted for password:
--
could not receive data from client: Connection reset by peer
--
2011/3/24 Jaroslav Záruba
> The command line is still the same, when executed under one user it does
> not ask for
The command line is still the same, when executed under one user it does not
ask for password, when executed under another (root that is) it does:
pg_dump --ignore-version --host=localhost --port=5432 --username=postgres
--file="$BACKUP_FILE" --format=p --column-inserts --encoding=UTF-8 db123
2011
Le 24/03/2011 10:05, Jaroslav Záruba a écrit :
> My pg_hba.conf looks like this:
>
> local all postgrestrust
> host all postgres 192.168.1.0/24 md5
> local all all ident
> host all all 127.0.0.1/32 md5
> host all all ::1/128 md5
>
>
Still lacks the complete pg_dump command lines (bo
My pg_hba.conf looks like this:
local all postgrestrust
host all postgres 192.168.1.0/24 md5
local all all ident
host all all 127.0.0.1/32 md5
host all all ::1/128 md5
2011/3/24 Guillaume Lelarge
> Please, answer to the list.
>
(Wrong button, I'm sorry for that.)
> Le 24/03/2011
Please, answer to the list.
Le 24/03/2011 09:13, Jaroslav Záruba a écrit :
> Yes, it is the password for PostgreSQL.
>
> pg_dump: [archiver (db)] connection to database "db123" failed: FATAL:
> password authentication failed for user "postgres"
> FATAL: password authentication failed for user "
Zitat von "Md. Rakibul Islam" :
Dear Mr. / Ms.
I want to introduce myself, me Md. Rakibul Islam from LEADS
Corporation Limited. For your kind deliberation, LEADS Corporation
is a ISO 9001:2000 certified IT services provider. LEADS delivers a
broad portfolio of IT services and solutions
Le 24/03/2011 08:34, Jaroslav Záruba a écrit :
> Hello
>
> I have pg_dump command in cron that accesses PostgreSQL under user postgres
> and does not provide a password.
>
> pg_dump --username=postgres ...
>
> I have set in pg_hba.conf that user postgres should be trusted for all
> databases fro
Hello
I have pg_dump command in cron that accesses PostgreSQL under user postgres
and does not provide a password.
pg_dump --username=postgres ...
I have set in pg_hba.conf that user postgres should be trusted for all
databases from localhost.
local all postgres trust
When I run the command un
19 matches
Mail list logo
