Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: Application name patch - v4


  • From: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
  • To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • Cc: Dave Page <dpage(at)pgadmin(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
  • Subject: Re: Application name patch - v4
  • Date: Mon, 30 Nov 2009 22:11:11 +0100
  • Message-id: <A2B6281C-8F03-4C48-A14C-F8B36E77A3C5@hi-media.com> <text/plain>

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 this or 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







Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group