On Wed, Mar 27, 2013 at 8:22 AM, Robert Haas wrote:
> On Wed, Mar 27, 2013 at 10:47 AM, Tom Lane wrote:>>
>> Use a service file maybe? But you can't have it both ways: either we
>> like the behavior of libpq absorbing defaults from the postmaster
>> environment, or we don't. You were just argui
On Wed, Mar 27, 2013 at 10:47 AM, Tom Lane wrote:
> Robert Haas writes:
>> On Wed, Mar 27, 2013 at 10:20 AM, Tom Lane wrote:
>>> It's arguable that we should unsetenv all of these inside the postmaster
>>> (once it's absorbed the values from the ones it historically pays
>>> attention to), so th
Robert Haas writes:
> On Wed, Mar 27, 2013 at 10:20 AM, Tom Lane wrote:
>> It's arguable that we should unsetenv all of these inside the postmaster
>> (once it's absorbed the values from the ones it historically pays
>> attention to), so that the postmaster environment does not impinge on
>> the
On Wed, Mar 27, 2013 at 10:20 AM, Tom Lane wrote:
> Robert Haas writes:
>> On Mon, Mar 25, 2013 at 4:38 AM, Albe Laurenz
>> wrote:
>>> If possible, I would suggest the following defaults (that's what I as
>>> a user would expect without thinking too hard):
>>> 1) Default the user to the current
Robert Haas writes:
> On Mon, Mar 25, 2013 at 4:38 AM, Albe Laurenz wrote:
>> If possible, I would suggest the following defaults (that's what I as
>> a user would expect without thinking too hard):
>> 1) Default the user to the current effective database user.
>> 2) Default the port to 5432.
>>
On Mon, Mar 25, 2013 at 4:38 AM, Albe Laurenz wrote:
> I agree that this is an unhappy situation.
>
> If possible, I would suggest the following defaults (that's what I as
> a user would expect without thinking too hard):
> 1) Default the user to the current effective database user.
> 2) Default t
Tom Lane wrote:
> It struck me while looking at the regression test arrangements for
> postgres_fdw that as things are set up, the default username for
> outgoing connections is going to be that of the operating system
> user running the postmaster. dblink is the same way.
>
> Now, this might not
Jeff Davis writes:
> On Fri, 2013-03-22 at 12:19 -0400, Tom Lane wrote:
>> Is there a better way to handle all this? It may be too late to rethink
>> dblink's behavior anyhow, but perhaps it's not too late to change
>> postgres_fdw. I think though that once we let 9.3 out the door, it
>> *will*
On Fri, 2013-03-22 at 12:19 -0400, Tom Lane wrote:
> Is there a better way to handle all this? It may be too late to rethink
> dblink's behavior anyhow, but perhaps it's not too late to change
> postgres_fdw. I think though that once we let 9.3 out the door, it
> *will* be too late to make any ma
It struck me while looking at the regression test arrangements for
postgres_fdw that as things are set up, the default username for
outgoing connections is going to be that of the operating system
user running the postmaster. dblink is the same way.
Now, this might not be the world's worst defaul
10 matches
Mail list logo
