On Wed, Apr 7, 2010 at 5:30 AM, Dave Page wrote:
> On Wed, Apr 7, 2010 at 10:16 AM, Magnus Hagander wrote:
>> Uh, why fallback_application_name? Isn't this the *exact* usecase
>> where "application_name" should be used? At least for the two apps -
>> fallback_app_name might be correct for dblink.
On Wed, Apr 7, 2010 at 10:16 AM, Magnus Hagander wrote:
> Uh, why fallback_application_name? Isn't this the *exact* usecase
> where "application_name" should be used? At least for the two apps -
> fallback_app_name might be correct for dblink.
>
> And yes, I think it's a good idea to set it for at
On Wed, Apr 7, 2010 at 10:21, Takahiro Itagaki
wrote:
>
> Fujii Masao wrote:
>
>> By default, the application_name of pgbench is "[unknown]". But I think
>> that pgbench should use fallback_application_name as psql, pg_dump,
>> etc does. Is it worth creating the patch?
>
> If we will take care of
Fujii Masao wrote:
> By default, the application_name of pgbench is "[unknown]". But I think
> that pgbench should use fallback_application_name as psql, pg_dump,
> etc does. Is it worth creating the patch?
If we will take care of fallback_application_name for contrib modules,
we need to fix no
Hi,
By default, the application_name of pgbench is "[unknown]". But I think
that pgbench should use fallback_application_name as psql, pg_dump,
etc does. Is it worth creating the patch?
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent
