| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Neil Conway <neilc(at)samurai(dot)com>, Marko Kreen <markokr(at)gmail(dot)com> |
| Subject: | Re: RESET command seems pretty disjointed now |
| Date: | 2007-04-16 23:15:44 |
| Message-ID: | 11931.1176765344@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> writes:
> Tom Lane wrote:
>> The current documentation for RESET exhibits a certain lack of, um,
>> intellectual cohesiveness:
>>
>> Synopsis
>>
>> RESET configuration_parameter
>> RESET ALL
>> RESET { PLANS | SESSION | TEMP | TEMPORARY }
> Maybe DISCARD for the plans etc might be more intuitive than extending
> RESET?
DISCARD PLANS and DISCARD TEMP seem pretty reasonable, but DISCARD SESSION
sounds a bit odd --- it seems like it might mean "disconnect", which of
course is exactly what we're trying to avoid. But possibly we could
rename RESET SESSION as DISCARD ALL.
Leastwise I haven't got any better ideas. Anyone have another proposal?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aidan Van Dyk | 2007-04-16 23:22:20 | Re: Hacking on PostgreSQL via GIT |
| Previous Message | Tom Lane | 2007-04-16 23:03:10 | Re: Hacking on PostgreSQL via GIT |