Solved using the recommendation:
"Change the 2 md5 to trust and all will work"
in the pg_hba.conf file
thanks again Francisco
Bill
On Thu, Dec 29, 2011 at 6:07 PM, Guillaume Lelarge
wrote:
> On Thu, 2011-12-29 at 17:47 +, Bill Appelbe wrote:
> > Solved
>
> It would be great to say how you s
On Fri, 2011-12-30 at 08:50 +, Bill Appelbe wrote:
> Solved using the recommendation:
> "Change the 2 md5 to trust and all will work"
> in the pg_hba.conf file
>
You do know what trust means, right? no check of any password? meaning
anyone can connect to your database with the highest permiss
Are there any other suggestions?
It also does not answer why it worked last week and not now
Bill
On Fri, Dec 30, 2011 at 9:07 AM, Guillaume Lelarge
wrote:
> On Fri, 2011-12-30 at 08:50 +, Bill Appelbe wrote:
> > Solved using the recommendation:
> > "Change the 2 md5 to trust and all will wo
On Fri, 2011-12-30 at 09:42 +, Bill Appelbe wrote:
> Are there any other suggestions?
> It also does not answer why it worked last week and not now
>
Well, no because the steps you show above seem the good ones. But saying
your problem is solved by using trust is wrong.
The only suggestion I
On 30/12/2011 08:02, Milan Bulatović wrote:
> Hello Raymond
>
> You are right, file pg_hba.conf exist in folder Data.
>
> I put next active line in it
>
> hostall all 192.168.1.24md5
>
> How it look like when open pg_hba.conf with pgAdmin3 you see in atta
My users have requested access to PLR for defining UDFs in Postgres on
GreenPlum DCA. When I installed R and ran the CREATE LANGUAGE the PLR
language option was defined as not trusted, I believe this is because
there is no validator function.
Is there a default validator function available for
On Fri, 2011-12-30 at 13:18 -0500, Schade, Jeffrey wrote:
> My users have requested access to PLR for defining UDFs in Postgres on
> GreenPlum DCA. When I installed R and ran the CREATE LANGUAGE the PLR
> language option was defined as not trusted, I believe this is because
> there is no validator
