Re: Application name patch - v4 - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: Application name patch - v4
Date
Msg-id A2B6281C-8F03-4C48-A14C-F8B36E77A3C5@hi-media.com
Whole thread Raw
In response to Re: Application name patch - v4  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Application name patch - v4
List pgsql-hackers
Le 30 nov. 2009 à 00:25, Tom Lane a écrit :
> The thing is that the libpq API treats application_name as a *property
> of the connection*.

Oh. Yeah.

> We could add a third keyword, say SET DEFAULT, that would have the
> behavior of setting the value in a fashion that would persist across
> resets.  I'm not sure that DEFAULT is exactly le mot juste here, but
> agreeing on a keyword would probably be the hardest part of making it
> happen.

I vaguely remember you explaining how hard it would be to be able to predict the value we RESET to as soon as we add
thisor that possibility. That's very vague, sorry, but only leaves a bad impression on the keyword choice
(bikeshedding,I should open a club). 

So what about SET CONNECTION application_name TO 'whatever'?

Regards,
--
dim






pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Block-level CRC checks
Next
From: Simon Riggs
Date:
Subject: Re: Block-level CRC checks