Re: authentication failure

On 04/15/2018 06:22 PM, armand pirvu wrote: Sorry for the late reply. In and out sll sorts of things which do distract me. I raised the authentication_timeout and seems okay for now I would take the 'for now' as a heads up that there is underlying issue that will need to be resolved

Re: authentication failure

> On Apr 12, 2018, at 10:07 AM, armand pirvu wrote: > > >> On Apr 12, 2018, at 9:55 AM, Adrian Klaver > > wrote: >> >> On 04/12/2018 07:50 AM, armand pirvu wrote: >> I would be inclined to raise the authentication_timeout first before setting the a

Re: Password encryption

On 04/15/2018 05:22 PM, Azimuddin Mohammed wrote: Hello, Is there a way I can encrypt the default password column of db user password. I know by default the password is encrypted as md5, can we encrypt that of shadow column for password? Are you talking about this view?: https://www.postgres

Password encryption

Hello, Is there a way I can encrypt the default password column of db user password. I know by default the password is encrypted as md5, can we encrypt that of shadow column for password? Thanks in advance

Re: hardcode password in connect string

El 15/04/18 a las 12:16, Raymond O'Donnell escribió: > On 15/04/18 12:35, Ricardo Martin Gomez wrote: >> Hello David, >> I think so, the parameter you need in psql command is -w mipassword. > > Sorry, this is not correct. -w causes psql *never* to prompt for a > password, and -W forces a password

Re: hardcode password in connect string

2018-04-15 17:16 GMT+02:00 Raymond O'Donnell : > On 15/04/18 12:35, Ricardo Martin Gomez wrote: > >> Hello David, >> I think so, the parameter you need in psql command is -w mipassword. >> > > Sorry, this is not correct. -w causes psql *never* to prompt for a > password, and -W forces a password p

Re: hardcode password in connect string

On 15/04/18 12:35, Ricardo Martin Gomez wrote: Hello David, I think so, the parameter you need in psql command is -w mipassword. Sorry, this is not correct. -w causes psql *never* to prompt for a password, and -W forces a password prompt. Neither allows the password to be passed as an argumen

Re: Can a broken Postgresql data directory be reconstructed without losing data?

On Sun, Apr 15, 2018 at 08:25:05AM +, A A wrote: > I'm trying to restore a database from a broken data directory that > have lost many of its files accidentally. Let me guess, a wild set of rm commands? > I have tried unsuccessfully to install new instance of the same > Postgresql version and

Re: Can a broken Postgresql data directory be reconstructed without losing data?

Well this doesn't address the question at all. On Sunday, April 15, 2018, 1:44:00 PM GMT+2, Ricardo Martin Gomez wrote: You must to restore a database from a backup. Regards. Obtener Outlook para Android From: A A Sent: Sunday, April 15, 2018 5:25:05 AM To: pgsql-general@lists.postg

Re: cursor "x" does not exist

Hello Bob, On Sat, 2018-04-14 at 15:44 +0100, Bob Jones wrote: > Hello, > > > > P.S. As a side-question, if anyone here has experience in using > Postgres as a backend to PHP, are refcursors the way to go or should > I > be thinking of SETOF or other return styles ? > If you have a business

Re: Can a broken Postgresql data directory be reconstructed without losing data?

You must to restore a database from a backup. Regards. Obtener Outlook para Android From: A A Sent: Sunday, April 15, 2018 5:25:05 AM To: pgsql-general@lists.postgresql.org Subject: Can a broken Postgresql data directory be reconstructed w

Re: hardcode password in connect string

Hello David, I think so, the parameter you need in psql command is -w mipassword. But, you have to understand that use this form or set PGPASSWORD aren't safer. Exist a file (pg_hba.conf) for this process ir task. Regards Obtener Outlook para Android ___

Can a broken Postgresql data directory be reconstructed without losing data?

I'm trying to restore a database from a broken data directory that have lost many of its files accidentally. I have tried unsuccessfully to install new instance of the same Postgresql version and then copy (with overwrite) the broken datadir to the new one.here the remaining datadir that I'm w