Re: [GENERAL] Fwd: dblink_connect fails

2016-01-10 Thread James Sewell 
Oops forgot to reply back to this one in the Christmas shutdown.

It turned out in this (new) install on Windows Postgres was running as the
Network Service user (??).

This was causing the issue, changed to Postgres and I was all good.

Cheers,


James Sewell,
Solutions Architect
__


Level 2, 50 Queen St, Melbourne VIC 3000

*P *(+61) 3 8370 8000  *W* www.lisasoft.com  *F *(+61) 3 8370 8099


On Thu, Dec 17, 2015 at 4:04 PM, Adrian Klaver 
wrote:

> On 12/16/2015 06:10 PM, James Sewell wrote:
>
>> Oops left off the list.
>>
>> -- Forwarded message --
>> From: *James Sewell* > >
>> Date: Thursday, 17 December 2015
>> Subject: dblink_connect fails
>> To: Joe Conway >
>>
>>
>> On Thu, Dec 17, 2015 at 12:11 PM, Joe Conway > > wrote:
>>
>> On 12/16/2015 04:53 PM, James Sewell wrote:
>> > No it is not.
>> >
>> > Just in case I tried setting it to 'postgres', logged in without -U
>> > (doesn't work without PGUSER set) and tried the operation again.
>>
>> > > DETAIL:  FATAL:  role "PRDSWIDEGRID01$" does not exist
>>
>> That "PRDSWIDEGRID01$" is coming from somewhere in your environment.
>> Looks like it is supposed to be a variable of some sort which is
>> supposed to resolve to an actual postgres user but for some reason
>> doesn't.
>>
>> What about FDWs?
>>
>>
>> This is a new database with some tables and dblink loaded.
>>
>> The  PRDSWIDEGRID01 is actually the hostname - but I just can't see how
>> it's getting injected.
>>
>> My understanding was that psql -U should override? And also that any
>> user variable just sets the user PostgreSQL variable - which is postgres.
>>
>> Strange stuff. I've just tried from cygwin, from Windows psql and from
>> PGAdmin - all the same result.
>>
>
> That is all from the client point of view. As Joe Conway has mentioned you
> need to be looking from the server point of view. In other words what is
> the environment for the Postgres server you are running dblink_connect in?
>
>
>>
>>
>> --
>> Crunchy Data - http://crunchydata.com
>> PostgreSQL Support for Secure Enterprises
>> Consulting, Training, & Open Source Development
>>
>>
>>
>>
>>
>> --
>>
>> James Sewell,
>> PostgreSQL Team Lead / Solutions Architect
>> __
>>
>> Level 2, 50 Queen St, Melbourne VIC 3000
>>
>> *P *(+61) 3 8370 8000***W* www.lisasoft.com *F *(+61) 3 8370 8099
>>
>>
>> 
>> The contents of this email are confidential and may be subject to legal
>> or professional privilege and copyright. No representation is made that
>> this email is free of viruses or other defects. If you have received
>> this communication in error, you may not copy or distribute any part of
>> it or otherwise disclose its contents to anyone. Please advise the
>> sender of your incorrect receipt of this correspondence.
>>
>>
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>

-- 


--
The contents of this email are confidential and may be subject to legal or 
professional privilege and copyright. No representation is made that this 
email is free of viruses or other defects. If you have received this 
communication in error, you may not copy or distribute any part of it or 
otherwise disclose its contents to anyone. Please advise the sender of your 
incorrect receipt of this correspondence.

Re: [GENERAL] Fwd: dblink_connect fails

2015-12-16 Thread Adrian Klaver 

On 12/16/2015 06:10 PM, James Sewell wrote:

Oops left off the list.

-- Forwarded message --
From: *James Sewell* >
Date: Thursday, 17 December 2015
Subject: dblink_connect fails
To: Joe Conway >


On Thu, Dec 17, 2015 at 12:11 PM, Joe Conway > wrote:

On 12/16/2015 04:53 PM, James Sewell wrote:
> No it is not.
>
> Just in case I tried setting it to 'postgres', logged in without -U
> (doesn't work without PGUSER set) and tried the operation again.

> > DETAIL:  FATAL:  role "PRDSWIDEGRID01$" does not exist

That "PRDSWIDEGRID01$" is coming from somewhere in your environment.
Looks like it is supposed to be a variable of some sort which is
supposed to resolve to an actual postgres user but for some reason
doesn't.

What about FDWs?


This is a new database with some tables and dblink loaded.

The  PRDSWIDEGRID01 is actually the hostname - but I just can't see how
it's getting injected.

My understanding was that psql -U should override? And also that any
user variable just sets the user PostgreSQL variable - which is postgres.

Strange stuff. I've just tried from cygwin, from Windows psql and from
PGAdmin - all the same result.


That is all from the client point of view. As Joe Conway has mentioned 
you need to be looking from the server point of view. In other words 
what is the environment for the Postgres server you are running 
dblink_connect in?






--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development





--

James Sewell,
PostgreSQL Team Lead / Solutions Architect
__

Level 2, 50 Queen St, Melbourne VIC 3000

*P *(+61) 3 8370 8000***W* www.lisasoft.com *F *(+61) 3 8370 8099



The contents of this email are confidential and may be subject to legal
or professional privilege and copyright. No representation is made that
this email is free of viruses or other defects. If you have received
this communication in error, you may not copy or distribute any part of
it or otherwise disclose its contents to anyone. Please advise the
sender of your incorrect receipt of this correspondence.




--
Adrian Klaver
adrian.kla...@aklaver.com


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[GENERAL] Fwd: dblink_connect fails

2015-12-16 Thread James Sewell 
Oops left off the list.

-- Forwarded message --
From: *James Sewell* 
Date: Thursday, 17 December 2015
Subject: dblink_connect fails
To: Joe Conway 


On Thu, Dec 17, 2015 at 12:11 PM, Joe Conway > wrote:

> On 12/16/2015 04:53 PM, James Sewell wrote:
> > No it is not.
> >
> > Just in case I tried setting it to 'postgres', logged in without -U
> > (doesn't work without PGUSER set) and tried the operation again.
>
> > > DETAIL:  FATAL:  role "PRDSWIDEGRID01$" does not exist
>
> That "PRDSWIDEGRID01$" is coming from somewhere in your environment.
> Looks like it is supposed to be a variable of some sort which is
> supposed to resolve to an actual postgres user but for some reason doesn't.
>
> What about FDWs?
>

This is a new database with some tables and dblink loaded.

The  PRDSWIDEGRID01 is actually the hostname - but I just can't see how
it's getting injected.

My understanding was that psql -U should override? And also that any user
variable just sets the user PostgreSQL variable - which is postgres.

Strange stuff. I've just tried from cygwin, from Windows psql and from
PGAdmin - all the same result.

>
>
> --
> Crunchy Data - http://crunchydata.com
> PostgreSQL Support for Secure Enterprises
> Consulting, Training, & Open Source Development
>
>



-- 

James Sewell,
PostgreSQL Team Lead / Solutions Architect
__


Level 2, 50 Queen St, Melbourne VIC 3000

*P *(+61) 3 8370 8000  *W* www.lisasoft.com  *F *(+61) 3 8370 8099

-- 


--
The contents of this email are confidential and may be subject to legal or 
professional privilege and copyright. No representation is made that this 
email is free of viruses or other defects. If you have received this 
communication in error, you may not copy or distribute any part of it or 
otherwise disclose its contents to anyone. Please advise the sender of your 
incorrect receipt of this correspondence.

Re: [GENERAL] Fwd: dblink_connect fails

2015-12-16 Thread Joe Conway 
On 12/16/2015 06:10 PM, James Sewell wrote:
> Oops left off the list.

Me too -- response repeated below...

> -- Forwarded message --
> From: *James Sewell*  >
> Date: Thursday, 17 December 2015
> Subject: dblink_connect fails
> To: Joe Conway >
> 
> 
> On Thu, Dec 17, 2015 at 12:11 PM, Joe Conway  > wrote:
> 
> On 12/16/2015 04:53 PM, James Sewell wrote:
> > No it is not.
> >
> > Just in case I tried setting it to 'postgres', logged in without -U
> > (doesn't work without PGUSER set) and tried the operation again.
> 
> > > DETAIL:  FATAL:  role "PRDSWIDEGRID01$" does not exist

> This is a new database with some tables and dblink loaded.
> 
> The  PRDSWIDEGRID01 is actually the hostname - but I just can't see how
> it's getting injected.
> 
> My understanding was that psql -U should override? And also that any
> user variable just sets the user PostgreSQL variable - which is postgres.

Hmmm, well the way you start up psql should be irrelevant here.

What goes on with dblink_connect() is more-or-less completely controlled
by libpq's PQconnectdb(). When you do not provide a user explicitly in
your libpq connect string it defaults to the user that the current
process is running under unless the PGUSER environment variable has been
defined. See:

http://www.postgresql.org/docs/9.4/interactive/libpq-envars.html

"The following environment variables can be used to select default
 connection parameter values, which will be used by PQconnectdb,
 PQsetdbLogin and PQsetdb if no value is directly specified by the
 calling code.

 PGUSER behaves the same as the user connection parameter."

-and-

http://www.postgresql.org/docs/9.4/interactive/libpq-connect.html#LIBPQ-PARAMKEYWORDS

"user

PostgreSQL user name to connect as. Defaults to be the same as
the operating system name of the user running the application."

So in your case, does your postgres server run as an OS user called
PRDSWIDEGRID01$ for some reason?

Joe



-- 
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development



signature.asc
Description: OpenPGP digital signature