Thread: Selecting the logfile

Selecting the logfile

From
Maximilian Tyrtania
Date:
There is this popup menu in the server status window, that says "aktuelle Logdatei" (=current logfile). Unfortunately
itis *sometimes* disabled. I have no clue as to why or what i should do to be able to look at the previous logfiles.
Anypointers? 
I'm on pgAdmin 1.12.2 on Mac OS 10.6.7. The Server is pg 9.0.2 on Ubuntu.

Best,

Max



Re: Selecting the logfile

From
Guillaume Lelarge
Date:
Le 17/04/2011 15:52, Maximilian Tyrtania a écrit :
> There is this popup menu in the server status window, that says "aktuelle Logdatei" (=current logfile). Unfortunately
itis *sometimes* disabled. I have no clue as to why or what i should do to be able to look at the previous logfiles.
Anypointers?
 
> I'm on pgAdmin 1.12.2 on Mac OS 10.6.7. The Server is pg 9.0.2 on Ubuntu.
> 

If you don't have something like "logging_collector not enabled or
log_filename misconfigured" or "redirect_std_err not enabled or
log_filename misconfigured" in the log pane, then it's probably because
you haven't selected the log pane.


-- 
Guillaumehttp://www.postgresql.frhttp://dalibo.com


Re: Selecting the logfile

From
Maximilian Tyrtania
Date:
Am 17.04.2011 um 16:07 schrieb Guillaume Lelarge:

> Le 17/04/2011 15:52, Maximilian Tyrtania a écrit :
>> There is this popup menu in the server status window, that says "aktuelle Logdatei" (=current logfile).
Unfortunatelyit is *sometimes* disabled. I have no clue as to why or what i should do to be able to look at the
previouslogfiles. Any pointers? 
>> I'm on pgAdmin 1.12.2 on Mac OS 10.6.7. The Server is pg 9.0.2 on Ubuntu.
>>
>
> If you don't have something like "logging_collector not enabled or
> log_filename misconfigured" or "redirect_std_err not enabled or
> log_filename misconfigured" in the log pane, then it's probably because
> you haven't selected the log pane.

Indeed, clicking on the log pane enables that popup menu. Maybe this could be improved upon.
Anyway, thanks for your help.

Maximilian Tyrtania Software-Entwicklung
Dessauer Str. 6-7
10969 Berlin
http://www.contactking.de

Re: Selecting the logfile

From
Guillaume Lelarge
Date:
Le 17/04/2011 16:36, Maximilian Tyrtania a écrit :
> Am 17.04.2011 um 16:07 schrieb Guillaume Lelarge:
> 
>> Le 17/04/2011 15:52, Maximilian Tyrtania a écrit :
>>> There is this popup menu in the server status window, that says "aktuelle Logdatei" (=current logfile).
Unfortunatelyit is *sometimes* disabled. I have no clue as to why or what i should do to be able to look at the
previouslogfiles. Any pointers?
 
>>> I'm on pgAdmin 1.12.2 on Mac OS 10.6.7. The Server is pg 9.0.2 on Ubuntu.
>>>
>>
>> If you don't have something like "logging_collector not enabled or
>> log_filename misconfigured" or "redirect_std_err not enabled or
>> log_filename misconfigured" in the log pane, then it's probably because
>> you haven't selected the log pane.
> 
> Indeed, clicking on the log pane enables that popup menu. Maybe this could be improved upon.
> Anyway, thanks for your help.
> 

Actually, the improvement was to make it that way. You only have access
to available tools for the selected pane. You don't need the cancel
query button if you didn't select a row in the activity pane or the lock
pane which has a query running. You don't need the logfile selection
combobox if you're not on the log pane.


-- 
Guillaumehttp://www.postgresql.frhttp://dalibo.com


Re: Selecting the logfile

From
Maximilian Tyrtania
Date:
Am 17.04.2011 um 17:13 schrieb Guillaume Lelarge:

>> Indeed, clicking on the log pane enables that popup menu. Maybe this could be improved upon.
>> Anyway, thanks for your help.
>
> Actually, the improvement was to make it that way. You only have access
> to available tools for the selected pane. You don't need the cancel
> query button if you didn't select a row in the activity pane or the lock
> pane which has a query running. You don't need the logfile selection
> combobox if you're not on the log pane.

Ah, i see, fair enough. Otoh, I've never been a big fan of this "disable controls and let the user figure out why they
aredisabled"-school of UI-Design. In my apps i let my controls enabled and show an alert explaining why they can't be
usedunder the current circumstances (or use a helptag). Saves me from having to deal with a lot of support incidents,
likethis one. 

And in this particular window, your enabling-strategy would be easier to grasp, if the controls that "work together"
wouldbe located next to each other. 

Just my 2 cents.

Max

Maximilian Tyrtania Software-Entwicklung
http://www.contactking.de