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.
Same result.
Cheers,
James Sewell,
PostgreSQL Team Lead / Solutions Architect
__
Level 2, 50 Queen St,
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
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.
Do you mean this:
DETAIL: FATAL: role "PRDSWIDEGRID01$" does not exist
or that you could not
Perhaps the attached will help. It's a sample function that I wrote and
tested a few years ago on PG v8.3
It worked then, so it should be a good model for you.
On Wed, Dec 16, 2015 at 8:00 PM, Adrian Klaver
wrote:
> On 12/16/2015 04:53 PM, James Sewell wrote:
>
>> No
On 12/15/2015 06:24 PM, James Sewell wrote:
> I have a Windows PostgreSQL server where dblink_connect fails to pick up
> the current user as follows:
> ffm=# SELECT dblink_connect('master', 'dbname=ffm');
> ERROR: could not establish connection
> DETAIL: FATAL: role
Hey all,
I have a Windows PostgreSQL server where dblink_connect fails to pick up
the current user as follows:
#psql -h localhost -U postgres ffm
ffm=# select version();
version
-
PostgreSQL 9.4.5, compiled