| From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, "Massa\, Harald Armin" <chef(at)ghum(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Application name patch - v2 |
| Date: | 2009-10-20 20:33:10 |
| Message-ID: | m2r5sxpzzt.fsf@hi-media.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> 2009/10/20 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> "psql" or "java". The cases that are actually useful are the ones where
>> the application sets it. I don't think we should have a default at all
>> --- you don't set it, you don't get a name.
>
> For psql, yes.
What about having psql -f foo.sql using 'psql: foo.sql' or sth as the
default value?
--
dim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Price | 2009-10-20 21:03:42 | Using pgcrypt to meet PCI compliance? |
| Previous Message | Tom Lane | 2009-10-20 20:10:12 | Re: Privileges and inheritance |